I realized a day or two ago that I wasn't myself sure how we are or should be using the "fixed in master" and "fixed in stable" statuses in Trac now that we have the 2.3.x branch. I.e., if something is fixed in the master branch and in 2.3.x, how is that to be noted? Are things "fixed in stable" when they are fixed in 2.3.x? Or are they only "fixed in stable" when they are fixed in 2.2.x? I'd suppose it was the latter, but that might make it difficult to know which bugs we can close when 2.3.0 is released.
Here's a proposal: (i) Use "fixed in master" to mean precisely that. (ii) If a bug is fixed in 2.3.x, then mark it "fixed in stable". If it's intended for 2.2.x but has not yet been pushed to 2.2.x, then set the milestone to 2.2.x. If it's not intended for 2.2.x, then set the milestone to 2.3.0. (iii) If a bug is fixed in 2.2.x (as well as 2.3.x), then set the milestone to 2.2.4. Thus: A bug marked "fixed in stable" with milestone 2.2.4 is one that has been fixed in 2.2.x; a bug marked "fixed in stable" with milestone NOT 2.2.4 has not been fixed in 2.2.x, and if the milestone is 2.3.0, then it is not going to be fixed in 2.2.x. Thoughts? Another idea might be temporarily to use some keyword. I have a dim memory we might have done that before. Richard
