Project

Profile

Help

Release Schedule » History » Sprint/Milestone 21

semyers, 08/01/2016 05:27 PM

1 8 amacdona@redhat.com
# Pulp 2.10 Release Schedule
2
3 20 semyers
|                           |                             |
4
| ------------------------- | --------------------------- |
5
| 2016-06-28                | 2.9 GA Planned Release Date |
6
| 2016-07-19                | Feature freeze              |
7
| ~~2016-07-26~~ 2016-08-02 | Beta, Branches created      |
8
| ~~2016-08-02~~ 2016-08-09 | Release candidate           |
9
| ~~2016-08-09~~ 2016-08-16 | GA Release                  |
10
11
Many features included in the feature freeze for this are still in review, which has caused a slip of the release timeline for the release. The Beta and subsequent releases will be arriving one week later than planned.
12 18 semyers
13
# Pulp 2.11 Release Schedule
14
15
|            |                              |
16
| ---------- | ---------------------------- |
17
| 2016-08-09 | 2.10 GA Planned Release Date |
18
| 2016-08-30 | Feature freeze               |
19
| 2016-09-06 | Beta, Branches created       |
20
| 2016-09-13 | Release candidate            |
21
| 2016-09-20 | GA Release                   |
22 8 amacdona@redhat.com
23 21 semyers
# Future Releases
24
25
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.
26
27 1 rbarlow
# Definitions
28
29 8 amacdona@redhat.com
**Beta** - All bug fixes that need to be in the release are complete. Dev believes the release is ready.  
30 1 rbarlow
**Feature Freeze** - No new features allowed after this date. Though exceptions can be made for work waiting on review, the submitter should attempt to have work reviewed and merged before the freeze date.  
31 8 amacdona@redhat.com
**Release Candidate** (RC) - QE has performed their testing and is satisfied to release. No new bug fixes after this point. Regressions or other urgent bug fixes will be handled case by case. There are no release candidates for Z releases.  
32 12 semyers
**Generally Available** (GA) - Release is generally available in the stable repositories.  
33
**Dev branch** - Branch created for Z (bugfix) release code changes related to a Generally Available Y release.
34 9 amacdona@redhat.com
35 1 rbarlow
# Y Release Cadence
36
37
The Y release cycle begins on the day of the previous GA Y release.
38 12 semyers
39 1 rbarlow
  - week 0: (Y-1) Previous Y Generally Available Release
40
  - week 3: Feature Freeze
41 13 semyers
  - week 4: Beta Y release
42 12 semyers
      - dev branch created for this Y Release
43
      - build system adapted to build from dev branch
44
      - master branch now tracks development for next Y release
45 13 semyers
      - beta is built from dev branch
46 12 semyers
  - week 5: Y Release Candidate
47
  - week 6: Generally Available Y Release
48
49
# Z Release Cadence
50 11 amacdona@redhat.com
51 13 semyers
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.
52 9 amacdona@redhat.com
53 12 semyers
  - week 0: (Z-1) Previous Z GA Release
54
  - week 1: Beta Z Release
55
  - week 2: GA Z Release
56 13 semyers
57
Z releases are released as often as possible based on this schedule.