Simone Rota [2006-03-18 23:54]:
1. Someone builds devtest isos. These are for testing ISO ports only and get the core system into a consistent state. During this period: - The trunk only contains the ports that are on the ISO
There is no trunk directory, I guess you mean the crux-2.2 (resp the release we're working on) directory in SVN?
- the previous version port tree get all the updates and continues to work as usual. (I think the devtest phase is generally the longest one)
Okay.
2. Once we're satisfied with the most recent devtest, we release a RC. The RC has a n-days lifespan (say 14). During these days: - maintainers will test and update their ports for the RC - only security fixes goes into the prev. release port tree - no changes are made to the core/opt ports included in the ISO to favour consistency.
So only in this stage I would be allowed to import non-iso-ports to crux-2.2 (resp next release)? If so, what if opt/some-non-iso-port shows a serious regression in core/gcc? I think it would make sense to add stage 1.5: - has fixed timeframe - maintainers add remaining ports to svn - their respective maintainers test them on devtest systems Depending on whether stage 1.5 shows serious problems in core ports, we'd either go back to stage 1 or proceed with stage 2.
3. If there are no reported problems the RC becomes the final release (otherways another RC is published). After the release: - port updates are generally applied only to the newly released port tree - we should keep a period in which we backport security fixes to the old port tree (we may as well have a dedicated volunteer / contributor)
Fine with me. Regards, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?