|
|
|
|
|
by engerland
2882 days ago
|
|
We already have our bug tracker for the engineers so why do twice the work? Most engineers don't care once the product is 'out' they only care what they're working on. So we create our change log (they are part of our 'release notes' actually) with only the user in mind but we reference the bug tracker number next to it. This is what we check in to the 'source' for the release notes. Then when we post to the 'outside world' we just remove those tracker numbers (takes a few seconds). That way the engineer can see the 'easy to understand conceptually' bug fix/enhancement and if they want to know more then they can see the Tracker reference and go and look up the 'real meat - with all the discussion and threads etc. For those bug fixes that we 'don't' document we have our source code software. |
|