Release Schedule » History » Sprint/Milestone 47
bizhang, 06/28/2017 07:51 PM
1 | 28 | semyers | # Releases In Progress |
---|---|---|---|
2 | |||
3 | 29 | semyers | # Future Releases |
4 | |||
5 | 44 | bizhang | - [[2.14.0 Release Status]] |
6 | 47 | bizhang | - [[2.13.3 Release Status]] |
7 | 44 | bizhang | |
8 | 29 | semyers | Following the 2.11 release, Pulp development will have transitioned almost entirely to working on the upcoming Pulp 3 release. Any releases after Pulp 2.11 will be scheduled as-needed. |
9 | 26 | semyers | |
10 | 24 | semyers | # Release Stages |
11 | 1 | rbarlow | |
12 | 24 | semyers | **Beta** - Dev believes the release is complete and ready for testing. Any bug fixes related to this release are still acceptable. |
13 | **Release Candidate** (RC) - Only bug fixes related to regressions, upgrade failures, or similar severity are accepted at this point. |
||
14 | **Generally Available** (GA) - Release is generally available in the stable repositories. |
||
15 | |||
16 | ## Release Stage Conditions |
||
17 | |||
18 | Releases spend a minimum time of one week in a given release stage. Subsequent releases in a given stage do not "reset the clock" on this waiting period. Care is taken to verify release-breaking bugs prior to advancing to the next release stage, which usually adds a few days to the release cycle, preventing "rapid-fire" releases. |
||
19 | |||
20 | ### Z Release Beta |
||
21 | |||
22 | There are no release candidates for Z releases. Z releases advance directly to GA after testing reveals no new blocking issues, and have passed acceptance testing by QE (including upgrade testing). |
||
23 | |||
24 | ### Y Release Beta |
||
25 | |||
26 | Y releases advance to RC after testing reveals no new blocking issues, and have passed acceptance testing by QE (not including upgrade testing). |
||
27 | |||
28 | ### Y Release RC |
||
29 | |||
30 | This release stage cannot advance to GA until the upgrade path from previous versions of pulp is confirmed to be working. |
||
31 | |||
32 | 1 | rbarlow | # Y Release Cadence |
33 | 12 | semyers | |
34 | 24 | semyers | Due to the unpredictable timeline of the release schedule once a Beta is released, the Y release cycle begins on the day of the previous **Beta** Y release. While unpredictable, the 12-week period between beta releases should be more than adequate to get that release Generally Available and still allow a few weeks before the next Beta is announced. |
35 | 1 | rbarlow | |
36 | 24 | semyers | - week 0: (Y-1 Release) Previous Y release cycle begins with a Beta Release |
37 | - week 12: (Y Release) Y release cycle begins with a Beta Release |
||
38 | - dev branch created for this Y Release, preventing the addition of new features. |
||
39 | 1 | rbarlow | - build system adapted to build from dev branch |
40 | - master branch now tracks development for next Y release |
||
41 | - beta is built from dev branch |
||
42 | 24 | semyers | - week 12+1?: Y release advances through Beta stage to RC as stage conditions are met. Release schedule is no longer time-based. |
43 | - week 12+2?: Y release advances through RC phase to GA as stage conditions are met. |
||
44 | 1 | rbarlow | |
45 | 24 | semyers | This release cadence was introduced to coincide with the release of the 2.11.0 Beta on 2016/10/25. If desired, the previous Y release cadence can be seen in the history of this wiki document. |
46 | |||
47 | 1 | rbarlow | # Z Release Cadence |
48 | |||
49 | 37 | semyers | The Z release cycle starts with a beta released roughly every three weeks. A beta Z release should begin place two weeks after the previous Z release becomes Generally Available. The Z release will spend a minimum of one week in Beta before being eligible to become Generally Available. |
50 | 12 | semyers | |
51 | - week 0: (Z-1) Previous Z GA Release |
||
52 | 37 | semyers | - week 2: Beta Z Release |
53 | - week 3: GA Z Release |
||
54 | 12 | semyers | |
55 | 24 | semyers | Z releases are released as often as possible based on this schedule, but are subject to upgrade testing which often extends the beta period beyond a week. |
56 | |||
57 | # Version Numbering |
||
58 | |||
59 | To the best of our ability, our releases adhere to semantic versioning. The releases in this document correspond to releases that increment a given release component (Y or Z) as defined by semantic versioning: |
||
60 | |||
61 | http://semver.org/#spec-item-2 |
||
62 | |||
63 | In short, a "Z Release" increments the "Z" release component (e.g. 1.0.0 -\> 1.0.1), and indicates no new features; only bug and security fixes have taken place. A "Y Release" increments the "Y" release component (e.g. 1.0.0 -\> 1.1.0), and indicates that new features have been introduced, but backward-incompatible API changes have not taken place. |
||
64 | 1 | rbarlow | |
65 | "X" Releases are not covered by this document. At the moment, they are rare enough as to be handled case-by-case. The next X release, Pulp 3, is currently being actively discussed on the pulp-dev mailing list. If you're interested in participating, go here to subscribe: |
||
66 | |||
67 | https://www.redhat.com/mailman/listinfo/pulp-dev |
||
68 | 33 | semyers | |
69 | 1 | rbarlow | # Past Releases |
70 | 33 | semyers | |
71 | 1 | rbarlow | Versions listed here have already become Generally Available, and are included here for historical reference. 2.11.2 was the first release to have a release status page in this wiki. |
72 | |||
73 | 46 | bizhang | - [[2.13.2 Release Status]] |
74 | 45 | bizhang | - [[2.13.1 Release Status]] |
75 | 41 | bizhang | - [[2.13.0 Release Status]] |
76 | 40 | bizhang | - [[2.12.2 Release Status]] |
77 | 35 | bizhang | - [[2.12.1 Release Status]] |
78 | 34 | semyers | - [[2.11.2 Release Status]] |
79 | - [[2.12.0 Release Status]] |