![]() | |||||||||||||
Messages in this thread |
>Should it be "-rc1"? Or "-pre1" to show it's not really considered release >quality yet? Or should I make like a rocket scientist, and count _down_ >instead of up? Should I make names based on which day of the week the >release happened? Questions, questions.. > >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. It's not only Linux which has this problem. For some of my own regularly updated "projects" (i.e. a collection of scripts) I use an always increasing number, preferably date, and do not care at all about -pre, -post, -beta, -rc, -etc. "2.6.10-27" (read: try #27)... sound funny. Jan Engelhardt -- Gesellschaft für Wissenschaftliche Datenverarbeitung Am Fassberg, 37077 Göttingen, www.gwdg.de - 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 | |||||||||||||