[upstream] Update the Release cycle section
Update the content, add new exercise and remove the outdated diagram. Change-Id: I6152e45570be93ae84a99370ee60d2b9ff9129ed
This commit is contained in:
Ildiko Vancsa
KATO Tomoyuki
parent
8c35dc58c6
commit
4e2845d1d1
Binary file not shown.
|
Before Width: | Height: | Size: 27 KiB |
@ -10,159 +10,172 @@ What makes a release
|
|||||||
====================
|
====================
|
||||||
|
|
||||||
- A way to coordinate the development of multiple projects
|
- A way to coordinate the development of multiple projects
|
||||||
- Until Kilo "integrated release" meant a date when all the projects
|
- Release process is managed by the Release Management team
|
||||||
are released at the end of the development cycles
|
- Release models
|
||||||
- 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 release policy on
|
- *Common cycle with development milestones*
|
||||||
http://governance.openstack.org/reference/projects
|
- Common cycle with intermediary release
|
||||||
|
- Trailing the common cycle
|
||||||
|
- Independent release model
|
||||||
|
|
||||||
Planning : Design
|
.. note::
|
||||||
|
|
||||||
|
- Release management description:
|
||||||
|
http://docs.openstack.org/project-team-guide/release-management.html
|
||||||
|
- The training concentrates on the common cycle with the development
|
||||||
|
milestones as that is what most students will face with. The other types
|
||||||
|
should be described with examples.
|
||||||
|
|
||||||
|
Exercise
|
||||||
|
========
|
||||||
|
|
||||||
|
- Look up the release schedule for the current and past two OpenStack
|
||||||
|
release cycles
|
||||||
|
- Identify common caracteristics of these cycles
|
||||||
|
|
||||||
|
- Milestones
|
||||||
|
- Deadlines
|
||||||
|
- etc.
|
||||||
|
|
||||||
|
- Describe a release cycle based on the information you found
|
||||||
|
|
||||||
|
Common cycle with development milestones
|
||||||
|
========================================
|
||||||
|
|
||||||
|
- A coordinated way for projects to periodically create their deliverables
|
||||||
|
including testing and documentation
|
||||||
|
- Every cycle includes
|
||||||
|
|
||||||
|
- Planning and design activities
|
||||||
|
- Implementation work
|
||||||
|
|
||||||
|
- New features
|
||||||
|
- Bug fixes
|
||||||
|
- Testing
|
||||||
|
- Documentation
|
||||||
|
|
||||||
|
- Release preparation
|
||||||
|
- Release
|
||||||
|
|
||||||
|
Planning - Design
|
||||||
=================
|
=================
|
||||||
|
|
||||||
.. rst-class:: colleft
|
- Design activity is a continuous effort
|
||||||
|
- Planning for a release cycle starts at the end of the previous cycle
|
||||||
|
- It depends on each project how to organise the work at each cycle
|
||||||
|
|
||||||
- Planning stage is at the start of a cycle
|
- Spec/blueprint freeze
|
||||||
- Take a step back
|
- Prioritising items
|
||||||
- Focus on what we want to do for the next one
|
|
||||||
|
|
||||||
.. rst-class:: colright
|
- Generic intention behind planning
|
||||||
|
|
||||||
.. image:: ./_assets/01-01-release.png
|
- Take a step back
|
||||||
|
- Focus on what we want to do for the next one
|
||||||
|
|
||||||
Planning : Discuss
|
Planning - Discuss
|
||||||
==================
|
==================
|
||||||
|
|
||||||
.. rst-class:: colleft
|
- Prepare your idea for the public
|
||||||
|
|
||||||
- With our peers
|
- Discuss with your peers
|
||||||
- Feedback and comments
|
- Work on feedback and comments
|
||||||
- Create the corresponding blueprint
|
|
||||||
- 4 weeks, Design Summit on the third week
|
|
||||||
|
|
||||||
.. rst-class:: colright
|
- Capture your idea in a spec/blueprint
|
||||||
|
|
||||||
.. image:: ./_assets/01-01-release.png
|
Planning - Target
|
||||||
|
|
||||||
Planning : Target
|
|
||||||
=================
|
=================
|
||||||
|
|
||||||
.. rst-class:: colleft
|
- Submit the blueprints and/or specs
|
||||||
|
- Identify a target milestone
|
||||||
|
|
||||||
- File new blueprints and/or specs
|
- When in the cycle you intend to complete it
|
||||||
- Set a target milestone
|
- Project team helps you to identify the target milestone and register it
|
||||||
- When in the cycle they intend to complete it
|
in the tracking tool
|
||||||
- PTLs triage the submitted blueprints and set priority
|
|
||||||
|
|
||||||
.. rst-class:: colright
|
|
||||||
|
|
||||||
.. image:: ./_assets/01-01-release.png
|
|
||||||
|
|
||||||
Implementation : Milestone
|
|
||||||
==========================
|
|
||||||
|
|
||||||
.. rst-class:: colleft
|
|
||||||
|
|
||||||
- Pushed to Gerrit for peer review
|
|
||||||
- Weeks before the milestone publication date
|
|
||||||
- Milestone-proposed branch
|
|
||||||
- Feature-frozen
|
|
||||||
|
|
||||||
.. rst-class:: colright
|
|
||||||
|
|
||||||
.. image:: ./_assets/01-01-release.png
|
|
||||||
|
|
||||||
Implementation : freezes
|
|
||||||
========================
|
|
||||||
|
|
||||||
.. rst-class:: colleft
|
|
||||||
|
|
||||||
|
- The priority of the work item is set by the project team members or lead
|
||||||
- Feature proposal freeze
|
- Feature proposal freeze
|
||||||
|
|
||||||
- Not even proposals for features will be accepted
|
- The deadline for proposing new ideas for a release cycle
|
||||||
- Focus on bug-fixing
|
- The exact date depends on the projects
|
||||||
|
|
||||||
|
Exercise
|
||||||
|
========
|
||||||
|
|
||||||
|
- Find feature proposal deadlines in the current release schedule
|
||||||
|
|
||||||
|
Implementation
|
||||||
|
==============
|
||||||
|
|
||||||
|
- When your blueprint/spec is accepted
|
||||||
|
|
||||||
|
- Push code to Gerrit for review
|
||||||
|
- Upload your code as early as possible in the release cycle
|
||||||
|
|
||||||
|
- Deadlines for the code to get merged
|
||||||
|
|
||||||
|
- Depends on the priority of your work item
|
||||||
|
- Set by each project team
|
||||||
|
|
||||||
|
Implementation - Milestone
|
||||||
|
==========================
|
||||||
|
|
||||||
|
- Three development milestones during a release cycle
|
||||||
|
- Make useful reference points in time to organize the development cycle
|
||||||
|
- Milestones are tagged in the repository using b1, b2 and b3
|
||||||
|
- Overall feature freeze is the third milestone
|
||||||
|
|
||||||
|
Implementation - Freezes
|
||||||
|
========================
|
||||||
|
|
||||||
|
- Freeze dates depend on the type of activity
|
||||||
- Feature freeze
|
- Feature freeze
|
||||||
|
|
||||||
- New features will not be accepted, only fixes
|
- Code for new features will not be accepted
|
||||||
|
- Bug fixing activities are still ongoing
|
||||||
|
- More focus on testing
|
||||||
|
|
||||||
- String freeze
|
- String freeze
|
||||||
|
|
||||||
- All externally visible strings must be frozen
|
- All externally visible strings must be frozen
|
||||||
- This helps the i18n and Documentation projects
|
- This helps the I18n and Documentation projects
|
||||||
|
|
||||||
.. rst-class:: colright
|
|
||||||
|
|
||||||
.. image:: ./_assets/01-01-release.png
|
|
||||||
|
|
||||||
Release Candidates
|
Release Candidates
|
||||||
==================
|
==================
|
||||||
|
|
||||||
.. rst-class:: colleft
|
|
||||||
|
|
||||||
- After the last milestone
|
- After the last milestone
|
||||||
|
- Code stabilization period
|
||||||
|
- Main activities
|
||||||
|
|
||||||
- File bugs about everything you find
|
- Test the code and file bugs
|
||||||
- Prioritize bugs / bug triage
|
- Prioritize bugs / bug triage
|
||||||
- Write documentation
|
|
||||||
- Fix as many bugs as you can
|
|
||||||
|
|
||||||
.. rst-class:: colright
|
- Get critical and high priority bugs fixed on the first place
|
||||||
|
- Fix as many bugs as possible
|
||||||
|
|
||||||
.. image:: ./_assets/01-01-release.png
|
- Finalize documentation
|
||||||
|
|
||||||
Release candidate 1
|
Release candidate 1
|
||||||
===================
|
===================
|
||||||
|
|
||||||
.. rst-class:: colleft
|
- Cut when all the release-critical bugs are fixed
|
||||||
|
- stable/release branch
|
||||||
- Between the last milestone and the RC1
|
- master branch is open for development
|
||||||
|
- 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
|
|
||||||
|
|
||||||
.. image:: ./_assets/01-01-release.png
|
|
||||||
|
|
||||||
Other release candidates
|
Other release candidates
|
||||||
========================
|
========================
|
||||||
|
|
||||||
.. rst-class:: colleft
|
|
||||||
|
|
||||||
- Regressions and integration issues
|
- Regressions and integration issues
|
||||||
|
|
||||||
- New release-critical bugs
|
- New release-critical bugs
|
||||||
|
|
||||||
- (RC2), with bugs targeted to it
|
- (RC2, RC3, ...), with bugs targeted to it
|
||||||
|
|
||||||
- Merged in the master branch first
|
- Merged in the master branch first and then cherry-picked to stable
|
||||||
- Repeated as many times as necessary
|
- Repeated as many times as necessary
|
||||||
|
|
||||||
.. rst-class:: colright
|
|
||||||
|
|
||||||
.. image:: ./_assets/01-01-release.png
|
|
||||||
|
|
||||||
Release day
|
Release day
|
||||||
===========
|
===========
|
||||||
|
|
||||||
.. rst-class:: colleft
|
|
||||||
|
|
||||||
- Last published release candidate
|
- Last published release candidate
|
||||||
- Published collectively as the OpenStack release
|
- Published collectively as the OpenStack release
|
||||||
|
|
||||||
.. rst-class:: colright
|
|
||||||
|
|
||||||
.. image:: ./_assets/01-01-release.png
|
|
||||||
|
|
||||||
Exercise
|
|
||||||
========
|
|
||||||
|
|
||||||
Based on the Kilo release schedule, find the URL of a document or a patch
|
|
||||||
that belongs to each of the steps.
|
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user