On Fri, Mar 28, 2014 at 9:27 AM, Jürgen Spitzmüller <sp...@lyx.org> wrote:
> 2014-03-28 8:57 GMT+01:00 Vincent van Ravesteijn <v...@lyx.org>: > > I implied if something is fixedinbranch it is either also fixedintrunk (or >> it was never in trunk). >> > > However, "fixed in trunk" implies to me that the bug _was_ in trunk. I > think it makes more sense for a branch-only bug to tag it "fixedinbranch" > only and set the milestone to the branch release. Or use another name that > does not imply that something was broken. > The status of a ticket is either "fixed in master" or "fixed in branch" or whatever, so whenever the bug has the status "fixed in stable" you don't know by status alone whether it was fixed in trunk before as well. It doesn't really matter I think. If it is "fixed in stable" and has a milestone 2.1.1, you know it is fixed. More info in the bug report as well. Do you prefer workflow as: new -> fixed in master -> fixed in master and stable -> closed(fixed) new -> fixed in stable -> closed(fixed) new -> fixed in stable -> fixed in master and stable -> closed(fixed) new -> fixed in master -> closed(fixed) We can do that as well of course. Vincent
