Project

Profile

Help

Release Schedule » History » Sprint/Milestone 22

semyers, 08/16/2016 07:49 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 22 semyers
| ~~2016-07-26~~ 2016-08-16 | Beta, Branches created      |
8
| ~~2016-08-02~~ 2016-08-23 | Release candidate           |
9
| ~~2016-08-09~~ 2016-08-30 | GA Release                  |
10 1 rbarlow
11 22 semyers
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. Additionally, blocking issues were discovered in other streams that were found to affect 2.10, adding further delay. With the release of the 2.9.2 hotfix and imminent release of 2.8.7, all known  
12
blocking issues are resolved and 2.10 is unblocked.
13 1 rbarlow
14 22 semyers
The schedule above is tentative, and may still change depending on the results of integration testing.
15
16 20 semyers
# Pulp 2.11 Release Schedule
17 22 semyers
18
**Due to the delays in the 2.10 mentioned above, it is likely that the 2.11 release will be delayed.**
19 18 semyers
20
|            |                              |
21
| ---------- | ---------------------------- |
22
| 2016-08-09 | 2.10 GA Planned Release Date |
23
| 2016-08-30 | Feature freeze               |
24
| 2016-09-06 | Beta, Branches created       |
25
| 2016-09-13 | Release candidate            |
26
| 2016-09-20 | GA Release                   |
27 8 amacdona@redhat.com
28 21 semyers
# Future Releases
29
30
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.
31
32 1 rbarlow
# Definitions
33
34 8 amacdona@redhat.com
**Beta** - All bug fixes that need to be in the release are complete. Dev believes the release is ready.  
35 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.  
36 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.  
37 12 semyers
**Generally Available** (GA) - Release is generally available in the stable repositories.  
38
**Dev branch** - Branch created for Z (bugfix) release code changes related to a Generally Available Y release.
39 9 amacdona@redhat.com
40 1 rbarlow
# Y Release Cadence
41
42
The Y release cycle begins on the day of the previous GA Y release.
43 12 semyers
44 1 rbarlow
  - week 0: (Y-1) Previous Y Generally Available Release
45
  - week 3: Feature Freeze
46 13 semyers
  - week 4: Beta Y release
47 12 semyers
      - dev branch created for this Y Release
48
      - build system adapted to build from dev branch
49
      - master branch now tracks development for next Y release
50 13 semyers
      - beta is built from dev branch
51 12 semyers
  - week 5: Y Release Candidate
52
  - week 6: Generally Available Y Release
53
54
# Z Release Cadence
55 11 amacdona@redhat.com
56 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.
57 9 amacdona@redhat.com
58 12 semyers
  - week 0: (Z-1) Previous Z GA Release
59
  - week 1: Beta Z Release
60
  - week 2: GA Z Release
61 13 semyers
62
Z releases are released as often as possible based on this schedule.