Hi, Dan Pascu <[email protected]> writes: > Just so that I understand the release process better, you say that a > release candidate will not be released if any change occurs, but it will > become the next release candidate; then when no changes are made to a > release candidate over a given time period, it is renamed to final and > released? Yes, that is how it works here, and I believe that is the traditional definition of release candidate. Unlike ours, some rules will let minor changes between RC and final. It's just more comfortable for the release manager (and I am a lazy person!) to make the rules stiffer, it comes with less responsibility and fewer hard decisions about individual fixes. The experience is that once you let in a trivial fix, someone with a slightly less trivial fix will appear and demand it being included. I believe the point releases are better suited for getting those last-minute fixes to public.
Yours, Petr. -- Peter Rockai | me()mornfall!net | prockai()redhat!com http://blog.mornfall.net | http://web.mornfall.net "In My Egotistical Opinion, most people's C programs should be indented six feet downward and covered with dirt." -- Blair P. Houghton on the subject of C program indentation _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
