Hi, On Fri, 18 Jan 2013 17:04:47 +0100 intrigeri <[email protected]> wrote: > [...] > > I've wondered a few times too, but since it looked like it works fine > like this is happening in reality, I've never felt in the mood of > raising the discussion. But I agree it's useful to clarify this at > some point :) > > Apparently, we always have stuff that looks good enough to be pushed > to our users in a few weeks, so we're eager to do it and we do. > I've been quite happy with this. One drawback of this approach is that > preparing a major release eats much time, that could be spent fixing > existing bugs and/or improving our infrastructure. > I wouldn't find it too bad to have to wait 12 weeks for inclusion of a feature, especially if it enables us to spend less time on releases and more on QA and developpement.
> I propose that if release N is a major one, the Release Manager(s) for > N+1 decide and announce (at least on tails-dev) whether N+1 is going > to be a major or minor one. The RM should make their decision known at > the very beginning of their release cycle (that is: when release N is > published), and if possible quite earlier (so that one can schedule > new features development accordingly, and not be sad to see stuff that > they worked hard to get in mergeable state on time be postponed at the > last minute). > > Rationale for having the RM decide: they are the ones who are the most > affected by this decision. > > What do you think? > Seems me good. Cheers _______________________________________________ tails-dev mailing list [email protected] https://mailman.boum.org/listinfo/tails-dev
