Project

Profile

Help

Release Schedule » History » Sprint/Milestone 82

ipanova@redhat.com, 01/22/2020 04:28 PM

1 28 semyers
# Releases In Progress
2
3 29 semyers
# Future Releases
4
5
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.
6 26 semyers
7 24 semyers
# Release Stages
8 1 rbarlow
9 80 ttereshc
**Beta** - Dev believes the Z release is complete and ready for testing. Any bug fixes related to this release are still acceptable.  
10
**Release Candidate** (RC) - Dev believes the Y release is complete and ready for testing. Any bug fixes related to this release are still acceptable.  
11 24 semyers
**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 1 rbarlow
### Y Release RC
22 24 semyers
23 80 ttereshc
There are no Beta for Y releases. Y releases advance to GA after testing reveals no new blocking issues, and have passed acceptance testing by QE. This release stage cannot advance to GA until the upgrade path from previous versions of pulp is confirmed to be working.  
24
There can be as many release candidates as needed.
25 1 rbarlow
26
# Y Release Cadence
27
28 80 ttereshc
~~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.~~
29 24 semyers
30 80 ttereshc
  - ~~week 0: (Y-1 Release) Previous Y release cycle begins with a Beta Release~~
31
  - week 0: (Y Release) Y release cycle begins with a Dev Freeze
32 57 pcreech
      - release branch created for this Y Release, preventing the addition of new features.
33 1 rbarlow
      - build system adapted to build from release branch
34
      - master branch now tracks development for next Y release
35 80 ttereshc
      - RC is built from release branch
36
  - week 1: (Y Release) Y RC Release
37
  - week 1+1?: Y release advances through RC phase to GA as stage conditions are met.
38 1 rbarlow
39 57 pcreech
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.
40
41 1 rbarlow
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
42
43
# Z Release Cadence
44 37 semyers
45 80 ttereshc
The Z release cycle starts with a Dev Freeze and then advances to a Beta. The Z release will spend a minimum of one week in Beta before being eligible to become Generally Available.
46 58 pcreech
47 80 ttereshc
  - week 0: Dev Freeze
48
  - week 1: Beta Z Release
49
  - week 1+1?: GA Z Release
50 12 semyers
51 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.
52
53
# Version Numbering
54
55
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:
56
57
http://semver.org/#spec-item-2
58
59
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.
60 1 rbarlow
61
"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:
62
63
https://www.redhat.com/mailman/listinfo/pulp-dev
64 33 semyers
65 71 rchan
# Release Schedule and Past Releases
66 33 semyers
67 71 rchan
Below is a list of all Versions including upcoming planned releases and versions already Generally Available listed for historical reference. 2.11.2 was the first release to have a release status page in this wiki.
68 1 rbarlow
69 82 ipanova@redhat.com
  - [[2.21.1 Release Schedule]]
70 81 dalley
  - [[2.21.0 Release Schedule]]
71 79 ttereshc
  - [[2.20.0 Release Schedule]]
72 78 ttereshc
  - [[2.19.1 Release Schedule]]
73 77 ttereshc
  - [[2.19.0 Release Schedule]]
74 76 rchan
  - [[2.18.1 Release Schedule]]
75 72 dkliban@redhat.com
  - [[2.18.0 Release Schedule]]
76 74 dkliban@redhat.com
  - [[2.17.1 Release Schedule]]
77 69 ipanova@redhat.com
  - [[2.17.0 Release Schedule]]
78 70 daviddavis
  - [[2.16.4 Release Status]]
79
  - [[2.16.3 Release Status]]
80 68 dkliban@redhat.com
  - [[2.16.2 Release Status]]
81 65 bmbouter
  - [[2.16.1 Release Status]]
82 63 bmbouter
  - [[2.16.0 Release Status]]
83 62 bmbouter
  - [[2.15.3 Release Status]]
84 61 daviddavis
  - [[2.15.2 Release Status]]
85 56 pcreech
  - [[2.15.1 Release Status]]
86 55 pcreech
  - [[2.15.0 Release Status]]
87 54 pcreech
  - [[2.14.3 Release Status]]
88 52 pcreech
  - [[2.14.2 Release Status]]
89 51 pcreech
  - [[2.14.1 Release Status]]
90 50 pcreech
  - [[2.13.4 Release Status]]
91 48 pcreech
  - [[2.14.0 Release Status]]
92
  - [[2.13.3 Release Status]]
93 46 bizhang
  - [[2.13.2 Release Status]]
94 45 bizhang
  - [[2.13.1 Release Status]]
95 41 bizhang
  - [[2.13.0 Release Status]]
96 40 bizhang
  - [[2.12.2 Release Status]]
97 35 bizhang
  - [[2.12.1 Release Status]]
98 34 semyers
  - [[2.11.2 Release Status]]
99
  - [[2.12.0 Release Status]]