On Fri, 16 Apr 2010 14:17:28 PDT, "F. Wessels" <wessels...@yahoo.com> wrote: > Thank you for the straight answer. > > This is a disappointment. I did indeed search for the 111b release for > example but was never able to find the branch. > I track a lot of bugs which affect my systems. But only a certain > development branch gives me the assurance that it was fixed. One can see > the fix in the repository and can track the bug in bugs.opensolaris.org. > But not for a release, they are never mentioned. Yes, I'm aware of bugzilla > but none for me relevant bugs are tracked there. If I understand your > explanation correctly than there's no way to find out what is actually in a > release. Not only what was fixed but also the code is not available. That > rather contradicts the OPEN part of opensolaris.
Bugzilla mostly covers distro and desktop bugs; ON bugs are in Bugster which has its data exported at bugs.opensolaris.org - these *are* updated for backported fixes. Also, the branches for the Desktop project are externally available. I'm not aware of a published changelog for each stable release, though. > Finally updates were never available. One could wait till the next release > or switch to a development branch. Take the 2009.06 release with the broken > CIFS part. A major service was broken and a fix was never available apart > from switching to a dev branch. > Stable releases do receive documented updates which require a paid support contract. > I don't want to sound ungrateful. I'm very thank for the great features > osol has given us. But the releases are a complete black box without > updates and the source for a release isn't available. I think the source > can be delivered without much cost and will give a lot of users peace of > mind. > > If I'm wrong or out of line please let me know. > I agree that publishing sources for the stable releases would be a great step toward transparency and in keeping with the spirit of the project, even if the processes remain internal, as is understandable for a corporate product. As it stands, to use the stable releases for anything other than an initial install, you're basically expected to have a support contract. This can put production users in a difficult position if a support contract for stable releases is not possible, since they may not have the resources to support development releases. >From the perspective of an outside contributor, the stable releases are much less relevant since they don't follow the development "mainline", but they do concern the project as they're the main vehicle for introducing new users to the software and the project. -Albert _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
