On Wednesday 04 April 2007 05:18 am, James Carlson wrote: > When the first major release binding project integrates, we've got a > problem. Those who still want to create minor releases will > essentially be unable to do so. At best, they'll be able to fork the > source at that point, and just "hope" that some of the subsequent > projects being done in the current gate can be retooled to fit in the > old one without too much trouble. > > It's likely that this situation would not last long. Major release > binding projects, by their very nature, are disruptive things.
But does the community have any binding projects on the code? > > What if the train just kept rolling and the distributions were > > responsible for their own decisions on what is major/minor for them? I > > realize this could cause some confusion where distributions don't have > > the same major levels and such, but at some point the distributions are > > going to be different. I see that more at the distribution level to > > determine when/how the major minor effects their distributions. > > That sounds like chaos to me. I think it depends on the perspective. OpenSolaris, I'm told means all types of software, Xorg, GNOME, JDS, etc...and today this is all a part of OpenSolaris. But those packages are not directly usable with the actual OpenSolaris, or what has traditionally known as ON. Are you talking about tracking ON changes with releases to allow specific milestones to be met? Changes to core components that target specific functionality with completion expected to be a part of a version? > What is "major," "minor," or "micro" is an architectural matter, not > something that a distributor can "decide" on his own. Is it up to the community to decide that for those distributions? Let's say that changes are going into OpenSolaris to change the functionality of how OpenSolaris handles kernel threads (this is all hypothetical), and it is planned for v 4.0. At the same time Nexenta is releasing a new version of KDE which is such a significant change that they decide to call it a major relase. At some point the Nexenta folks need to decide, do they want for ON 4.0, or do they ship with 3.74b, that latest without those kernel thread changes. Even if you plan versions, they won't coincide with all distributions, I 'spose that's my point. > I suspect that distributions can make some important decisions about > content, and perhaps even determine when to pull a minor release out > of a string of minor-compatible changes, but that only the community > can make effective decisions about release binding. I don't see such a distinction. -- Alan DuBoff - Solaris x86 Engineering - IHV/OEM Group Advocate of Insourcing at Sun, hire people that care about our company! _______________________________________________ opensolaris-discuss mailing list [email protected]
