Project

Profile

Help

Release Schedule » History » Sprint/Milestone 16

semyers, 06/30/2016 12:59 AM

1 7 mhrivnak
# Pulp 2.9 Release Schedule
2 1 rbarlow
3 15 semyers
|                           |                         |                                                                   |
4
| ------------------------- | ----------------------- | ----------------------------------------------------------------- |
5
| 2016-06-07                | 2.9.0 Feature freeze    | Only bug fixes after this                                         |
6
| ~~2016-06-14~~ 2016-06-21 | 2.9.0 Beta              | dev branches created: Build system adapted to build from branches |
7 16 semyers
| ~~2016-06-28~~ 2016-06-30 | 2.9.0 Beta 2            |                                                                   |
8
| ~~2016-06-21~~ 2016-07-5  | 2.9.0 Release candidate | Final Freeze                                                      |
9
| ~~2016-06-28~~ 2016-07-12 | 2.9.0 GA Release        | Pulp 2.9 is Generally Available                                   |
10 14 semyers
11
2.9.0 Blockers:
12
13 15 semyers
  - ~~https://pulp.plan.io/issues/2035~~
14
  - ~~https://pulp.plan.io/issues/2037~~
15 3 rbarlow
16 13 semyers
Build infrastructure problems and a blocking bug pushed the beta release and all subsequent releases of 2.9 back one week.  
17
These delays have not affected the 2.10 release timeline.
18
19 8 amacdona@redhat.com
# Pulp 2.10 Release Schedule
20
21 13 semyers
|            |                        |
22
| ---------- | ---------------------- |
23
| 2016-06-28 | Previous Y GA Release  |
24
| 2016-07-19 | Feature freeze         |
25
| 2016-07-26 | Beta, Branches created |
26
| 2016-08-02 | Release candidate      |
27
| 2016-08-09 | GA Release             |
28 8 amacdona@redhat.com
29 1 rbarlow
# Definitions
30
31 8 amacdona@redhat.com
**Beta** - All bug fixes that need to be in the release are complete. Dev believes the release is ready.  
32 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.  
33 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.  
34 12 semyers
**Generally Available** (GA) - Release is generally available in the stable repositories.  
35
**Dev branch** - Branch created for Z (bugfix) release code changes related to a Generally Available Y release.
36 9 amacdona@redhat.com
37 1 rbarlow
# Y Release Cadence
38
39
The Y release cycle begins on the day of the previous GA Y release.
40 12 semyers
41 1 rbarlow
  - week 0: (Y-1) Previous Y Generally Available Release
42
  - week 3: Feature Freeze
43 13 semyers
  - week 4: Beta Y release
44 12 semyers
      - dev branch created for this Y Release
45
      - build system adapted to build from dev branch
46
      - master branch now tracks development for next Y release
47 13 semyers
      - beta is built from dev branch
48 12 semyers
  - week 5: Y Release Candidate
49
  - week 6: Generally Available Y Release
50
51
# Z Release Cadence
52 11 amacdona@redhat.com
53 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.
54 9 amacdona@redhat.com
55 12 semyers
  - week 0: (Z-1) Previous Z GA Release
56
  - week 1: Beta Z Release
57
  - week 2: GA Z Release
58 13 semyers
59
Z releases are released as often as possible based on this schedule.