Project

Profile

Help

Release Schedule » History » Sprint/Milestone 59

bmbouter, 02/26/2018 07:53 PM
Adding 2.15.3 release page

1 28 semyers
# Releases In Progress
2
3 29 semyers
# Future Releases
4
5 55 pcreech
  - [[2.16.0 Release Status]]
6 59 bmbouter
  - [[2.15.3 Release Status]]
7 56 pcreech
  - [[2.15.2 Release Status]]
8 44 bizhang
9 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.
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 57 pcreech
  - week 11: (Y Release) Y release cycle begins with a Dev Freeze
39
      - release branch created for this Y Release, preventing the addition of new features.
40
      - build system adapted to build from release branch
41 1 rbarlow
      - master branch now tracks development for next Y release
42 57 pcreech
      - beta is built from release branch
43
  - week 12: (Y Release) Y Beta Release
44 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.
45 1 rbarlow
  - week 12+2?: Y release advances through RC phase to GA as stage conditions are met.
46
47 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.
48 1 rbarlow
49 57 pcreech
2.y releases are no longer time based and therefore are not dependent on when previous y release beta was cut. The rest of the schedule is followed
50
51 1 rbarlow
# Z Release Cadence
52
53
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.
54 37 semyers
55 58 pcreech
  - week 0: (Z-1) Previous Z Beta Release
56
  - week 1: (Z-1) Previous Z GA Release
57
  - week 2: Dev Freeze
58
  - week 3: Beta Z Release
59
  - week 4: GA Z Release
60 12 semyers
61 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.
62
63
# Version Numbering
64
65
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:
66
67
http://semver.org/#spec-item-2
68
69
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.
70 1 rbarlow
71
"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:
72
73
https://www.redhat.com/mailman/listinfo/pulp-dev
74 33 semyers
75 1 rbarlow
# Past Releases
76 33 semyers
77 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.
78
79 56 pcreech
  - [[2.15.1 Release Status]]
80 55 pcreech
  - [[2.15.0 Release Status]]
81 54 pcreech
  - [[2.14.3 Release Status]]
82 52 pcreech
  - [[2.14.2 Release Status]]
83 51 pcreech
  - [[2.14.1 Release Status]]
84 50 pcreech
  - [[2.13.4 Release Status]]
85 48 pcreech
  - [[2.14.0 Release Status]]
86
  - [[2.13.3 Release Status]]
87 46 bizhang
  - [[2.13.2 Release Status]]
88 45 bizhang
  - [[2.13.1 Release Status]]
89 41 bizhang
  - [[2.13.0 Release Status]]
90 40 bizhang
  - [[2.12.2 Release Status]]
91 35 bizhang
  - [[2.12.1 Release Status]]
92 34 semyers
  - [[2.11.2 Release Status]]
93
  - [[2.12.0 Release Status]]