Project

Profile

Help

Release Schedule » History » Sprint/Milestone 29

semyers, 01/18/2017 04:31 PM

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