Project Overview and Current Status Jonas Arndt OpenSAF Technical Co-chair Jonas.Arndt@hp.com 2009-06-03 Shenzhen, China 1 1 1

Different Roles in the Technical Project Project Participation Presentation Outline Project Introduction Different Roles in the Technical Project Project Participation Branch Management Build Environment 2 2 2

Project Introduction OpenSAF Project OpenSAF Foundation Launched Mid 2007 OpenSAF Foundation Formed Jan 22nd 2008 Founded by Emerson Ericsson NSN HP SUN License LGPL V2.1 OpenSAF Foundation Today has 9 Members

Roles Within the Project Users Developers Maintainers TLC TCC Release Manager http://download.opensaf.org/foundation-docs/Technical_Operating_Proedures_V_1.1.0.pdf

Users The consumer of OpenSAF Builds applications that are using OpenSAF Participate on the user mailing list Suggest improvements Quality feedback and bug reporting

Developers Developers Maintainers Contribute code and/or documentation to OpenSAF Participate on devel mailing list Developers need to sign the OpenSAF ICPA A developer that owns a certain module Review bug fixes / patches Approves patches prior to check-in

Release Manager Manages Releases Announces code freeze deadlines Identifies outstanding blockers Determines when a release is stable Decides when a development release has quality to make GA

Roles - TLC TLC is a technical expert group responsible for leading the OpenSAF project Meet every week to discuss overall architectural goals and issues 8

The role of TLC Defines and maintains the OpenSAF roadmap Features Release times & Milestones Establish priorities for developing new services and features for existing services Appointing module owners Other stuff …. 9

The role of Technical Co-Chairs TCCs are elected by TLC Responsible for the leadership of the TLC Bridge between BoD and TLC Run the TLC meetings Mario, I have attached what I currently have Mario, I have attached what I currently have 172.16.174.1 TCC TLC BoD 10

Basic Feature Lifecycle I need Feat. A I’ll implement Feat. A Feat. A Feat. A ”Wish-list” User Developer Feat. A + Time Estimate Major Feature Feat A Feat B Feat C OpenSAF Roadmap Minor Feature TLC Release Manager Betas I have Feat. A ! Feat. B Milestones Feat. A Feat. C FC FC Detailed Plan for Release N RC M General Availability M User Dev Trunk Release N Stable Trunk OpenSAF Release N

Basic Release Lifecycle M M OpenSAF Release N Feature A Feature B Feature C Trunk Ms 0 Beta 1 Ms 1 Beta 2 Ms 2 Beta 3 FC RC1 (RC2) GA Patch Release Beta – new mafor feature is delivered to trunk Ms – Milestone, happens when Beta prooves stable FC – Feature Complete milestone, no new functional deliveries for that release RC – Release Candidate, potential to be a final product (GA), ready to release unless fatal bugs emerge. GA – General Availabilty

Project Participation Read FAQ - http://devel.opensaf.org/wiki/TechnicalFAQ Read OpenSAF Developers handbook - http://devel.opensaf.org/wiki/Handbook Subscribe to and read mailing lists Sign and fax the Individual Contributor Participation Agreement (ICPA) to +1-925-683-2623. You will get an account Read & Post to Mailing Lists! Contribute with code and bug fixes

Branch management OpenSAF will maintain a total of three(3) branches/Repositories at any given time One development branch New features and bug fixes Backward compatibility with previous releases may not be maintained. Two “stable” (“bug fix”) branches Bug fixes only Backward compatibility within the stable branch will always be maintained. OpenSAF will provide the following services for branches it maintains: “master” HG repository (source for individual clones) Release Management Archives at major milestones

Current Status (Maintained Branches) Branch Management Current Status (Maintained Branches) Release 3 (Current development branch) General Availability release (Early June) https://devel.opensaf.org/wiki/downloads/Release_3_downloads http://devel.opensaf.org/hg/opensaf Release 2 (Stable bug fix branch) Current patch level 2.0.1 https://devel.opensaf.org/wiki/downloads/Release_2_downloads http://devel.opensaf.org/hg/opensaf-2.x-stable

Post R3 (Maintained Branches) Release 4 (Development branch) Branch Management Post R3 (Maintained Branches) Release 4 (Development branch) Roadmap: http://devel.opensaf.org/wiki/Roadmap Release 3 (Stable bug fix branch) https://devel.opensaf.org/wiki/downloads/Release_3_downloads http://devel.opensaf.org/hg/opensaf-3.x-stable Release 2 (Stable bug fix branch) Current patch level 2.0.1 https://devel.opensaf.org/wiki/downloads/Release_2_downloads http://devel.opensaf.org/hg/opensaf-2.x-stable

OpenSAF Server Environment & System Administration Development, build and mail servers Initially hosted by HP Transitioned to external hosting provider System administration Questions & issues should be directed to the following list: opensaf-sysadmin@lists.linux.hp.com Working to have representation in the list for each geography Post R3 (Maintained Branches) 172.16.174.1