Project

Profile

Help

Release Schedule » History » Sprint/Milestone 15

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