diff --git a/doc/upstream-training/source/01-release-cycle.rst b/doc/upstream-training/source/01-release-cycle.rst index 5dc5d689..bbc228b5 100644 --- a/doc/upstream-training/source/01-release-cycle.rst +++ b/doc/upstream-training/source/01-release-cycle.rst @@ -6,14 +6,28 @@ OpenStack Release Cycle :class: fill :width: 100% +What makes a release +==================== + +- A way to coordinate the development of multiple projects +- Until Kilo "integrated release" meant a date when all the projects + are released at the end of the development cycles +- Integrated projects were also tested together at the gate +- For Liberty integrated projects are those managed by the Release + Management Team +- Other projects may have different schedules + + - Each project team page shows its releas policy on + http://governance.openstack.org/reference/projects + Planning : Design ================= .. rst-class:: colleft - Planning stage is at the start of a cycle -- take a step back -- focus on what we want to do for the next one +- Take a step back +- Focus on what we want to do for the next one .. rst-class:: colright @@ -25,8 +39,8 @@ Planning : Discuss .. rst-class:: colleft - With our peers -- feedback and comments -- create the corresponding blueprint +- Feedback and comments +- Create the corresponding blueprint - 4 weeks, Design Summit on the third week .. rst-class:: colright @@ -38,9 +52,9 @@ Planning : Target .. rst-class:: colleft -- file new blueprints and/or specs -- set a target milestone -- when in the cycle they intend to complete it +- File new blueprints and/or specs +- Set a target milestone +- When in the cycle they intend to complete it - PTLs triage the submitted blueprints and set priority .. rst-class:: colright @@ -52,10 +66,10 @@ Implementation : Milestone .. rst-class:: colleft -- pushed to our Gerrit review -- weeks before the milestone publication date -- milestone-proposed branch -- feature-frozen +- Pushed to Gerrit for peer review +- Weeks before the milestone publication date +- Milestone-proposed branch +- Feature-frozen .. rst-class:: colright @@ -66,19 +80,19 @@ Implementation : freezes .. rst-class:: colleft -* Feature proposal freeze +- Feature proposal freeze - * not even proposals for features will be accepted - * focus on bug-fixing + - Not even proposals for features will be accepted + - Focus on bug-fixing -* Feature freeze +- Feature freeze - * new features will not be accepted, only fixes + - New features will not be accepted, only fixes -* String freeze +- String freeze - * all externally visible strings must be frozen - * this helps the translation and documentation program + - All externally visible strings must be frozen + - This helps the i18n and Documentation projects .. rst-class:: colright @@ -90,10 +104,11 @@ Release Candidates .. rst-class:: colleft - After the last milestone -- file bugs about everything you find -- prioritize bugs / bug triage -- write documentation -- fix as many bugs as you can + + - File bugs about everything you find + - Prioritize bugs / bug triage + - Write documentation + - Fix as many bugs as you can .. rst-class:: colright @@ -105,10 +120,11 @@ Release candidate 1 .. rst-class:: colleft - Between the last milestone and the RC1 -- stop adding features and concentrate on bug fixes -- Once all the release-critical bugs are fixed, we produce the first release - candidate for that project (RC1) -- used as-is as the final release + + - Stop adding features and concentrate on bug fixes + - Once all the release-critical bugs are fixed, we produce the first release + candidate for that project (RC1) + - Used as-is as the final release .. rst-class:: colright @@ -120,11 +136,14 @@ Other release candidates .. rst-class:: colleft -- regressions and integration issues -- new release-critical bugs +- Regressions and integration issues + + - New release-critical bugs + - (RC2), with bugs targeted to it -- merged in the master branch first -- repeated as many times as necessary + + - Merged in the master branch first + - Repeated as many times as necessary .. rst-class:: colright @@ -135,8 +154,8 @@ Release day .. rst-class:: colleft -- last published release candidate -- published collectively as the OpenStack release +- Last published release candidate +- Published collectively as the OpenStack release .. rst-class:: colright @@ -145,5 +164,5 @@ Release day Exercise ======== -Based on the Icehouse release schedule, find the URL of a document or a patch +Based on the Kilo release schedule, find the URL of a document or a patch that belongs to each of the steps. diff --git a/doc/upstream-training/source/03-technical-committee.rst b/doc/upstream-training/source/03-technical-committee.rst index df98a57d..a69ef623 100644 --- a/doc/upstream-training/source/03-technical-committee.rst +++ b/doc/upstream-training/source/03-technical-committee.rst @@ -21,58 +21,24 @@ and generally has oversight over the OpenStack project entirely. .. image:: ./_assets/03-01-TC.png -OpenStack Programs -================== +OpenStack Project Teams +======================= -OpenStack "Programs" are efforts which are essential to the completion of the -OpenStack project mission. This mission is to produce the ubiquitous Open -Source cloud computing platform that will meet the needs of public and private -clouds regardless of size, by being simple to implement and massively -scalable. Programs can create any code repository and produce any deliverable -they deem necessary to achieve their goals. +Project Teams are teams of *people* using *tools* (code repository, +bug tracker, etc) and coordinated *processes* to produce a number of +*deliverables*, in order to achieve a clearly stated *objective*. -- The official list of programs is in the `governance` repository - - http://git.openstack.org/cgit/openstack/governance/tree/reference/programs.yaml -- The wiki page: https://wiki.openstack.org/wiki/Category:Programs - -List of Programs -================ - -.. rst-class:: colleft - -- Compute (Nova) -- Object Storage (Swift) -- Image Service (Glance) -- Identity (Keystone) -- Dashboard (Horizon) -- Networking (Neutron) -- Block Storage (Cinder) -- Telemetry (Ceilometer) -- Orchestration (Heat) -- Database Service (Trove) -- Bare metal (Ironic) - -.. rst-class:: colright - -- Common Libraries (Oslo) -- Queue service (Zaqar) -- Data processing (Sahara) -- Key management (Barbican) -- DNS Service (Designate) -- Shared File Systems (Manila) -- Infrastructure -- Documentation -- Quality Assurance (QA) -- Deployment (TripleO) -- Devstack (DevStack) -- Release cycle management - -Maintained on http://git.openstack.org/cgit/openstack/governance/tree/reference/programs.yaml +- The official list of projects is in the `governance` repository + - http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml +- Fully rendered http://governance.openstack.org/reference/projects/index.html Meetings ======== - Governance/TechnicalCommittee#Meeting + + - https://wiki.openstack.org/wiki/Meetings#Technical_Committee_meeting + - Agenda - Motions @@ -86,14 +52,14 @@ Exercise - read tc.2014-04-01-20.03.log.html and briefly comment on keystone document -Program Technical Leads (PTLs) -============================== +Project Team Leads (PTLs) +========================= - Manage day-to-day operations - Drive the program goals - Resolve technical disputes -Active Program Contributor (APC) +Active Project Contributor (APC) ================================= - Voters for a given program PTL diff --git a/doc/upstream-training/source/_assets/01-01-release.png b/doc/upstream-training/source/_assets/01-01-release.png index 7dfc054c..6080bf4e 100644 Binary files a/doc/upstream-training/source/_assets/01-01-release.png and b/doc/upstream-training/source/_assets/01-01-release.png differ