**draftDraft**
Note: please refer to previous discussion Business-level Requirements for TF Release Process
Initially, due to the absence of release definition and process, community release needs to be aligned with some Contrail commercial release. Once the Community establishes its own independent release definition and process, all commercial releases including contrail can be aligned to community release.
This alignment is necessary to allow migration between the community and commercial release. As long as this alignment is maintained, Commercial release can follow any other release frequencies.
Aligning with Contrail commercial release to begin with we have following options:
- We do a release out of old branch R1911 now to bridge the gap from the last community release of r5.1 and look forward to do next release in June, 2020 aligning with Contrail release of June -
- We skip the releases between r5.1 and R2002, and look forward to do next release in March, 2020 aligning with Contrail release of March
| Table of Contents |
|---|
The purpose of the release process
The Release Process is dedicated to creating a plan and then to following and monitoring that plan to deliver an increment to the product. It is extremely important, especially in a community where there are lots of developers from different companies, countries, to have a common understanding of what and how we would like to achieve. The release plan will help us to coordinate our efforts to achieve agreed goals and to deliver proper, coded, tested, and working as an expected increment of product. To achieve that, we need to act in accordance with agreed rules, time schedule, and milestones.
Prerequisites
...
- Read the Getting Started as a Contributor page (including Registration and User Creation, environment installation)
- Check/assign to one of the existing projects or create a proposal for a new project
Release Process
Release The release process is outlined as follows
- Invitation of proposals for features, enchancement enhancement requests
- Blueprints/Design/Architectural approval cut-off date (4 months before release date)
- Code delivery cut-off date (2 months before release date)
- Branch cut-off date (1 month before release date)
- Stablise Stabilize the branch and build daily builds for 1 month
- Release the stable build as Community Release
- Build weekly/bi-weekly if any change commited committed to the branch
...
Release
...
Cadence, Life Time & Support
The initial release cadence is planned for Proposal is to have a community release every 6 months.
Intially due to absence of release definition and process, community release needs to be aligned with some Contrail commerical release. Once Community establishes its own independent release definition and process, all commerical release including contrail can be aligned to community release.
This alignment is necessary to allow migration between community and commercial release. As long as this alignment is maintained, Commercial release can follow any other release frequencies.
Release Life Time & Support
The initial release process is waterfall-based, but the Community intends to move into a more agile approach in the future.
The Community intends to actively support Community will be actively supporting any release for up to 9 months, where any bug fixes will be committed and made available.LTS release: Community recognising a need to have Long term support release, will look forward to introduce a mechnism to term a community release as LTS release. where any LTS release will be actively supported by community for upto ?2/3 years?
Next Community Release
Aligning with Contrail commerical release to begin with we have following options:
...