[EMAIL PROTECTED] wrote:
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.)
I've already said this in an off-list reply, but I guess I'll say it again here.
Having everyone release their distribution from branches leaves us with the
gate entirely divorced from a binary deliverable. In that situation it
would get little to no testing. This is bad bad bad.
Now, if this were to be done (to use 'now' as an example) like this.
- Nevada stabilizes (becomes Sun's release branch).
- Nevada+1 appears (becomes the next MR gate)
- Installable builds from both continue to appear on the same bi-weekly
schedule
- belenix, nexenta, and whoever else are free (as they are now, and always
have been...) to create $THEM-r$WHATEVER branches for their release
engineering.
That would perhaps work, I think. (it would also be pretty much identical to
as things are already...)
On the other hand:
- onxx-gate --- "main" branch, yet nobody actually installs from it.
- sunonxx-gate --- Sun's branch, with builds (and SX/SXCR) coming from it.
- belonxx-gate --- Belenix branch, with their builds coming from that.
- .....
Would lead to merge hell, onxx-gate getting little actual testing, and would
be utterly catastrophic, in my view.
-- Rich
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
