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 :)
Oops, sorry, I forgot to push out the EOL "note", it's now there. As for marking something in the repo, given that the "normal" mode is that the tree expires after the next major release from Linus, there really isn't any need to point that out, right (hint, we've been doing that for 6+ years now without needing anything like that.) The big deal is notifying people of the "longterm" kernels, which so far, I think I've been doing well, with lkml and blog posts, as well as announcements at major conferences. If there's other places I should be doing those notifications, please let me know. thanks, greg k-h -- 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
