Project

Profile

Help

Release Schedule » History » Sprint/Milestone 24

semyers, 10/27/2016 05:42 PM
New Y Release Cadance, clarificiation of phase advancement conditionsand remove of obsolete terms.

1 1 rbarlow
# Future Releases
2 21 semyers
3 1 rbarlow
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.
4 21 semyers
5 24 semyers
A 2.12 release is expected but a date has not yet been set for this release.
6 1 rbarlow
7 24 semyers
# Release Stages
8 1 rbarlow
9 24 semyers
**Beta** - Dev believes the release is complete and ready for testing. Any bug fixes related to this release are still acceptable.  
10
**Release Candidate** (RC) - Only bug fixes related to regressions, upgrade failures, or similar severity are accepted at this point.  
11
**Generally Available** (GA) - Release is generally available in the stable repositories.
12
13
## Release Stage Conditions
14
15
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.
16
17
### Z Release Beta
18
19
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).
20
21
### Y Release Beta
22
23
Y releases advance to RC after testing reveals no new blocking issues, and have passed acceptance testing by QE (not including upgrade testing).
24
25
### Y Release RC
26
27
This release stage cannot advance to GA until the upgrade path from previous versions of pulp is confirmed to be working.
28
29 1 rbarlow
# Y Release Cadence
30 12 semyers
31 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.
32 1 rbarlow
33 24 semyers
  - week 0: (Y-1 Release) Previous Y release cycle begins with a Beta Release
34
  - week 12: (Y Release) Y release cycle begins with a Beta Release
35
      - dev branch created for this Y Release, preventing the addition of new features.
36 1 rbarlow
      - build system adapted to build from dev branch
37
      - master branch now tracks development for next Y release
38
      - beta is built from dev branch
39 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.
40
  - week 12+2?: Y release advances through RC phase to GA as stage conditions are met.
41 1 rbarlow
42 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.
43
44 1 rbarlow
# Z Release Cadence
45
46
The Z release cycle consists of alternating weekly beta and GA releases of bug & security fixes for Generally Available Y releases, built from a dev branch.
47 12 semyers
48
  - week 0: (Z-1) Previous Z GA Release
49
  - week 1: Beta Z Release
50 13 semyers
  - week 2: GA Z Release
51 12 semyers
52 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.
53
54
# Version Numbering
55
56
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:
57
58
http://semver.org/#spec-item-2
59
60
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.
61
62
"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:
63
64
https://www.redhat.com/mailman/listinfo/pulp-dev