Right. Another possible approach is to have a single OpenSolaris gate
(well, one per consolidation). Each distro would create its own stable
branch when it gets close to a release. (That branch could still be
visible, but it would be run by the distro, not by the community.)
This is similar to the branch management proposal that was outlined in
OpenSolaris Development Process draft that was circulated in November
2005. There is a relatively free-flowing trunk (in the proposal it was
always assumed to be running under Minor release binding rules) and a
distribution could branch off of the trunk. For more details, see the
section titled "Branch Management" in
http://www.opensolaris.org/os/community/on/os_dev_process/
If OpenSolaris has releases, then in addition to the transition issues
(from one release to the next), we also need to figure out how older
releases are managed and eventually retired.
Do any of the distros besides Solaris plan to issue patches for old
releases? If they do, then there's some benefit in having a common
source base, though I can imagine policy conflicts over what's worth
patching.
In the above proposal there is a single trunk - each distribution is
responsible for their own release branch(es) and so there wouldn't be a
common source base in this case (besides the ultimate source of the
trunk.)
dsc
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
