Project

Profile

Help

Release Schedule » History » Sprint/Milestone 39

pcreech, 04/12/2017 05:04 PM

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