On Fri, 16 Apr 2010 04:42:26 PDT, "F. Wessels" <wessels...@yahoo.com> wrote: > Hi all, > > how is a release (like osol 200906) tagged in the source repository? > Looking back in the repository I only see the onnv_xxx tags and not a > specific tag designating a final release. So where can one obtain the > source to build the release yourself? I know that there are request to > include a /usr/src but that's not the point.
Non-development builds are branched from a regular build for QA, including backporting fixes, 2009.06 was build 111b, which means it was the second "respin" of 111. AFAIK, these branches are only available internally to Sun/Oracle (and continue to be updated for /support). Also you should be aware that several consolidations (projects with separate repositories) are combined in each build. > > Another question is how can I find out what bug fixes where included in > the release? Take the upcoming 2010?? release for example. It was based on > onv_134. Upto onv_138 a torrent of bug fixes were putback. But also new > functionality. What is and is not included in the final release? > Any pointers to documentation of this process would be more than welcome. The CR for a bug is usually updated to indicate if a fix was backported (this may also be the case for Bugzilla entries which don't have a corresponding CR, but I'm not sure), but again, most of the release-related processes are internal to the company. Hope that makes sense, -Albert _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
