On Mon, Oct 27, 2008 at 8:59 PM, Krzysztof KosiĆski wrote:
By the way, I don't know what is imprecise about the Fix Committed status. To the user it says: it will be fixed in the next version, wait for it or download an SVN snapshot to get rid of this bug. To the developer it says: you don't need to work on this, somebody else already fixed it. I agree that in the context of a developer the difference between "Fix Committed" and "Fix Released" is minor - both say that you don't need to work on this issue. For users and release managers it is an important distinction.
Well, I agree with that. There is a "but" however.
The thing is that we fix *a lot* of bugs and commit *a lot* of patches during every release cycle. And it looks like we are moving towards a one-release-a-year release cycle. Which practically means that release wardens will have to somehow go through the whole bugtracker, find all "fix committed" in a time range and change them to "fix released". A *rough* estimation would give over 500 such cases. I know of no tools to ease this pain.
Alexandre