Valerie Anne Bubb writes: > On Mon, 2 Apr 2007, Mark J. Nelson wrote: > > 3. Rename Steve's onnv-gate repository to on-gate > > > > ...and put it under the ON Project. This shouldn't be tied to Nevada; > > when it's time to worry about releasing Nevada, then the onnv-gate (or > > maybe even on11-gate) repository should be created as a fork of > > on-gate. > > Why should we hide our internal forking & gate shifting from the outside?
Because it's an artifact of Sun's distribution that's not necessarily related to the work of any other distribution. In other words, all distributions need to be free to decide when they're cutting a release. Some may want to do it more often than the once-every-5-years-or-so that we do it. Some might even want fewer releases. It's plausible that some might want "no releases" at all and instead favor a stream of versioned packages. In any event, the point where we decide to fork is our problem, not other people's problem. It's possible that other distributions _might_ want to piggyback on our release scheduling. If so, then that may be a good reason to expose those forks, as the frozen code itself could still be kept open. But I do think that divorcing the community from our release process is helpful, in that the community has to start thinking about its own release process. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
