2 Dec 2011 18:06
Re: Version numbers after Lightning 1.0 (Summary)
Tony Mechelynck <antoine.mechelynck <at> gmail.com>
2011-12-02 17:06:22 GMT
2011-12-02 17:06:22 GMT
On 17/11/11 22:48, Philipp Kewisch wrote: > On 11/17/11 10:21 PM, Stefan Sitter wrote: >> Philipp Kewisch wrote: >>> But isn't the "Version" (not Target Milestone) field rather used for >>> "What version of the product does this bug show up in" ? If we have >>> Trunk and Lightning 1.3 at the same time, what version would one set for >>> a bug that happens in the current comm-central? >> >> In my opinion "Trunk" should not be used assigned in the future, neither >> for Version nor Target Milestone. A bug found in comm-central should be >> set to the currently active version, i.e. "Lightning 1.3" if found today. >> >> Currently we have 207 open and 1745 closed calendar bugs that use >> Version "Trunk". I don't think they should be moved to Version >> "Lightning 1.3". At least I assume this would happen if you rename the >> keyword instead of adding a new one. >> >> Stefan > Oh, right!Maybe we can move those bugs out of the way to the correct > version and then remove the Trunk milestone, otherwise new bugs might be > wrongly assigned. I'm adding Lightning 1.3 as a new milestone for now. > > Philipp Well, IIUC the idea of setting the Version field to Trunk is that that means "The problem happens in current trunk and will happen in all future trunk versions until it is fixed". OTOH if a problem is discovered in a branch build it may or may not happen also on trunk. On SeaMonkey (where current trunk is 2.8a1) if I discover a bug in a(Continue reading)
RSS Feed