On Sun, Oct 14, 2012 at 04:27:09PM +0200, Oliver wrote: > On Sunday 14 October 2012 06:20:21 Greg KH wrote: > > Ok, where can I be more "verbose" about this? > > My thinking was to place the (minimum) maintenance period/EOL dependency in > the git commit and/or tag annotation that you create for each new stable > release in the linux-stable.git repo, although, you could just do this for > the > first stable (3.x.1) but that would then depend on people being clued up > about > where to find it. Either way, having it in the Git commit or tag will make it > visible to Git users and anyone able to click on Gitweb links. > > The other option is to get it stated on kernel.org itself, but given that > there's still no (EOL) tag on 3.5.7 on the front page, I'm guessing that > getting this done is perhaps administratively arduous, or just one more > annoying item to potentially forget to do. If not, well, opportunity knocks :)
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 ? 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. 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
