![]() | |||||||||||||
Messages in this thread |
On Fri, Oct 22, 2004 at 03:05:13PM -0700, Linus Torvalds wrote: > And the fact is, I can't see the point. I'll just call it all "-rcX", > because I (very obviously) have no clue where the cut-over-point from > "pre" to "rc" is, or (even more painfully obviously) where it will become > the final next release. This should be easy: the cut-over should be when you're tempted to rename it 2.6.next. If you have no intention (or hope) of renaming 2.6.x-rc1 to 2.6.x, it is not a "release candidate" by definition. What's the point? It serves as a signal that a) we're not accepting more big changes b) we think it's ready for primetime and needs serious QA c) when 2.6.next gets released, the _exact code_ has gone through a test cycle and we can have some confidence that there won't be any nasty 0-day bugs when we go to install 2.6.next on a production machine. > (*) In other words, I had a beer and watched TV. Mmm... Donuts. Please devote some more beer and TV to this problem after you release 2.6.10. -- Mathematics is the supreme nostalgia of our time. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 14:07 [from the cache] ©2003-2008 | |||||||||||||