Project

Profile

Help

Release Schedule » History » Sprint/Milestone 20

semyers, 07/25/2016 04:02 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 1 rbarlow
# Definitions
24
25 8 amacdona@redhat.com
**Beta** - All bug fixes that need to be in the release are complete. Dev believes the release is ready.  
26 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.  
27 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.  
28 12 semyers
**Generally Available** (GA) - Release is generally available in the stable repositories.  
29
**Dev branch** - Branch created for Z (bugfix) release code changes related to a Generally Available Y release.
30 9 amacdona@redhat.com
31 1 rbarlow
# Y Release Cadence
32
33
The Y release cycle begins on the day of the previous GA Y release.
34 12 semyers
35 1 rbarlow
  - week 0: (Y-1) Previous Y Generally Available Release
36
  - week 3: Feature Freeze
37 13 semyers
  - week 4: Beta Y release
38 12 semyers
      - dev branch created for this Y Release
39
      - build system adapted to build from dev branch
40
      - master branch now tracks development for next Y release
41 13 semyers
      - beta is built from dev branch
42 12 semyers
  - week 5: Y Release Candidate
43
  - week 6: Generally Available Y Release
44
45
# Z Release Cadence
46 11 amacdona@redhat.com
47 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.
48 9 amacdona@redhat.com
49 12 semyers
  - week 0: (Z-1) Previous Z GA Release
50
  - week 1: Beta Z Release
51
  - week 2: GA Z Release
52 13 semyers
53
Z releases are released as often as possible based on this schedule.