Darren J Moffat wrote:
Stephen Hahn wrote:
* Mike Kupfer <[EMAIL PROTECTED]> [2007-01-11 10:25]:
"sch" == Stephen Hahn <[EMAIL PROTECTED]> writes:
sch> I'm quite happy with the discussion, although my inclination is
sch> to get the immediate term issue resolved and then spend some time
sch> thinking about how the endgame of a specific release is handled.
For the endgame issue, please include the question of how old releases
will be managed. I'm particularly concerned about security fixes, where
we currently try to have at least a preliminary patch ready at the time
a security flaw is announced.
Sounds fine. Are you talking about the theoretical case when all
releases under discussion are open development (or at least open
source), or today's case where only SMI has a collection of previous
releases?
The case were all releases are open source and there are no longer any
SMI only previous releases is by my rough calculation a minimum of 12
years away but more likely 15 years.
"previous releases with complete source encumbrance" is impossible to handle
(< 10), for Nevada and above, I can't think of any problem with sustaining
gates being available containing the open parts of the tree, for those parts
of the source base that are open (ON's usr/src, JDS, SFW, pkg tools, etc).
So I'm not entirely sure what you're referring to here, could you be more
explicit?
-- Rich
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
