On Sun, Oct 14, 2012 at 04:54:36PM +0200, Oliver wrote: > On Sunday 14 October 2012 16:39:13 Willy Tarreau wrote: > > > Oliver, it has already happened that a new version has followed the > > last one, so even saying this in the last commit could become confusing. > > Imagine if Greg decides to emit a 3.5.8 to satisfy a bunch of users > > experiencing early migration issues with 3.6, what would this tag mean > > in 3.5.7 then ? > > So, that's saying that "3.x will be EOL whenever 3.(x+1) comes out" is not > necessarily true in all cases, in that scenario, following my proposal would > ensure this is not a source of confusion since any changes to sunsetting > would > be right there in the tag annotation.
I think your did not understood, sometimes the decision changes *after* what was supposed to be the last release, so your information in the tag annotation would become more confusing, as someone would have a 3.5.7 tag saying "this is the last one" and later a 3.5.8 tag saying "finally this is the last one". In practice, if you're that much sensible to how long a stable release lasts, you should definitely switch to an LTS version (eg: 3.4 right now). > > Let's not add more burden in the management of releases, it's already a > > tedious work (and I still have a hard time imagining how Greg maintains > > that many versions in parallel), there's no need to think about adding > > even more considerations for each release. > > This may very well be true, although since he has to create the tag > annotation > regardless, I was hoping this would be of minimal additional effort. At least speaking for myself, if I had to do this, it would be one additional step in the release process. Each step comes with its own set of usual mistakes, we try to automatize as much as possible. > In any case I'm sure he can speak for himself. Probably he has better to do right now :-) Cheers, Willy -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
