Release Schedule » History » Sprint/Milestone 9
amacdona@redhat.com, 06/06/2016 05:21 PM
1 | 7 | mhrivnak | # Pulp 2.9 Release Schedule |
---|---|---|---|
2 | 1 | rbarlow | |
3 | 3 | rbarlow | | | | | |
4 | | ---------- | ----------------------- | ------------------------------------------- | |
||
5 | | 2016-05-17 | 2.9 branches created | Build system adapted to build from branches | |
||
6 | 6 | bmbouter | | 2016-06-07 | 2.9.0 Feature freeze | Only bug fixes after this | |
7 | 3 | rbarlow | | 2016-06-14 | 2.9.0 Beta | | |
8 | | 2016-06-21 | 2.9.0 Release candidate | Final Freeze | |
||
9 | | 2016-06-28 | 2.9.0 Release | | |
||
10 | 1 | rbarlow | |
11 | 8 | amacdona@redhat.com | # Pulp 2.10 Release Schedule |
12 | |||
13 | | | | |
||
14 | | ---------- | ----------------- | |
||
15 | | 2016-06-28 | Branches created | |
||
16 | | 2016-07-19 | Feature freeze | |
||
17 | | 2016-07-26 | Beta | |
||
18 | | 2016-08-02 | Release candidate | |
||
19 | | 2016-08-09 | GA Release | |
||
20 | |||
21 | 1 | rbarlow | # Definitions |
22 | |||
23 | 8 | amacdona@redhat.com | **Beta** - All bug fixes that need to be in the release are complete. Dev believes the release is ready. |
24 | **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. |
||
25 | **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. |
||
26 | |||
27 | 9 | amacdona@redhat.com | # Y Release Cadence |
28 | 8 | amacdona@redhat.com | |
29 | The release cycle will begin on the day of the previous GA release. |
||
30 | |||
31 | - 0 weeks: New branch created, build system adapted to build from branches |
||
32 | - 3 weeks: Feature freeze |
||
33 | - 4 weeks: Beta release |
||
34 | - 5 weeks: Release Candidate |
||
35 | 1 | rbarlow | - 6 weeks: GA Release |
36 | 9 | amacdona@redhat.com | |
37 | # Z Release Cadence |
||
38 | |||
39 | - 0 weeks: New Branch Created/Beta |
||
40 | - 1 weeks: Release Candidate |
||
41 | - 2 weeks: GA Release |