All, As you may have already seen a new Beta for OpenSAF was released today. So I thought it would be nice to outline what's next going forward. OpenSAF will follow a Release Pattern that involves the following release-points:
- Betas - Milestones - Release Candidates (RC) - General Availability (GA) Every major feature (read roadmap items) will constitute a Beta and only one of those major features will be checked-in to the opensaf trunk/main-repository at one time. Minor patches can be checked-in at any time. After a successful check-in to the trunk (read build tests) the Beta announcement will be done which will provide a tarball of the beta. The expectation is that the users, developers will take the release and test it, find issues, provide patches for issues etc. (note you have to become an opensaf developer to be able to send/suggest a patch). These bug-reports/patches etc. will be examined by the respective maintainers and addressed in some fashion. Once a significant amount of testing has been done on the Beta and the trunk is stable a Milestone will be announced by the Release Manager of OpenSAF. Currently Steve Constant ([EMAIL PROTECTED]) is the Release Manager for the first release of OpenSAF. At that point the next feature can be checked-in and the next Beta will be announced. This procedure will iterate until the last major milestone for a particular release has been checked in based on the OpenSAF roadmap (https://devel.opensaf.org/wiki/DraftRoadmap). At this point the Release is supposed to be "Feature Complete". That's when the first Release Candidate (RC) for a Release is announced. The idea is we'll iterate through as many Release candidates as needed until a stable GA can be announced. Again the Release Manager will make that decision as to when a release is stable enough to be GA-ed based on all the feedback that we get from the community. Release Numbering Scheme. We'll follow the Numbering scheme outlined below ... We will use a x.y.z numbering scheme like 1.0.7. - For Betas & Milestones increment 'z' and use odd number for Betas and even number for Milestones. (this is to quickly distinguish between the two) So we continue as 1.0.7 (Beta). 1.0.8, (milestone), 1.0.9 (Beta), 1.0.10 (Milestone.) ... [We could also use odd number for beta & even number for milestone, in that case next beta should be 1.0.7] - Increment 'y' by 1 and reset 'z' to 0 with the first release candidate. Hence the first RC would b e 1.1.0, 2nd RC 1.2.0 and so. - For a GA release increment 'x' by 1 and reset 'y' & 'z' to 0. So we have 2.0.0 for the first release. Then go back to 2.0.2/2.0.1 for the first Beta of release 2. Off-course feel free to suggest changes to the above. Sayan > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Murthy E-G19462 > Sent: Wednesday, February 13, 2008 7:58 AM > To: [email protected]; [EMAIL PROTECTED] > Subject: [Users] OpenSAF1.0.7 Release > > > OpenSAF foundation is pleased to announce OpneSAF1.0.7 > Release to the community. > > Following are the key features of the Release > > * OpenSAF infrastructure supports 32 bit and 64 bit > architectures (Tested for AMD64, Intel 64). > * Test infrastructure and test suites for all opensaf > services are included. > * Additional compliance to LSB (Linux Standard Base). > * OpenSAF thread stack size optimization, dynamic loading of > OpenSAF libraries in applications > * Additional bug fixes. > * Updates to the INSTALL instructions and dependent packages > and Changelog (Please read it before > posting queries to the distribution list) > > Nagendra, Mahesh, Mathivanan, Ramesh, and Vishal are the key > contributors (and many more)for the Release. > > The release can be accessed from below URL > > https://devel.opensaf.org/wiki/downloads > > The Source control system is also in place for OpenSAF (Based > of Mercurial). You can access the Repository using > > hg clone http://devel.opensaf.org/hg/opensaf > > Some basic tutorial on how to use opensaf source repository > is available in https://devel.opensaf.org/wiki/DevelGuide > > For details on how to use Mercurial you can always refer to > http://hgbook.red-bean.com/ > > > Regards > Murthy > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > _______________________________________________ > Users mailing list > [email protected] > http://list.opensaf.org/maillist/listinfo/users > ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________ Users mailing list [email protected] http://list.opensaf.org/maillist/listinfo/users
