Release Schedule » History » Revision 10
« Previous |
Revision 10/86
(diff)
| Next »
amacdona@redhat.com, 06/06/2016 05:29 PM
Z releases do not have an RC
Pulp 2.9 Release Schedule¶
| 2016-05-17 | 2.9 branches created | Build system adapted to build from branches |
| 2016-06-07 | 2.9.0 Feature freeze | Only bug fixes after this |
| 2016-06-14 | 2.9.0 Beta | |
| 2016-06-21 | 2.9.0 Release candidate | Final Freeze |
| 2016-06-28 | 2.9.0 Release |
Pulp 2.10 Release Schedule¶
| 2016-06-28 | Branches created |
| 2016-07-19 | Feature freeze |
| 2016-07-26 | Beta |
| 2016-08-02 | Release candidate |
| 2016-08-09 | GA Release |
Definitions¶
Beta - All bug fixes that need to be in the release are complete. Dev believes the release is ready.
Feature Freeze - No new features allowed after this date. Though exceptions can be made for work waiting on review, the submitter should attempt to have work reviewed and merged before the freeze date.
Release candidate - QE has performed their testing and is satisfied to release. No new bug fixes after this point. Regressions or other urgent bug fixes will be handled case by case.
Y Release Cadence¶
The release cycle will begin on the day of the previous GA release.
- 0 weeks: New branch created, build system adapted to build from branches
- 3 weeks: Feature freeze
- 4 weeks: Beta release
- 5 weeks: Release Candidate
- 6 weeks: GA Release
Z Release Cadence¶
- 0 weeks: New Branch Created
- 1 weeks: Beta Release
- 2 weeks: GA Release
Updated by amacdona@redhat.com over 8 years ago · 10 revisions
.