Release Schedule » History » Revision 22
Revision 21 (semyers, 08/01/2016 05:27 PM) → Revision 22/86 (semyers, 08/16/2016 07:49 PM)
# Pulp 2.10 Release Schedule | | | | ------------------------- | --------------------------- | | 2016-06-28 | 2.9 GA Planned Release Date | | 2016-07-19 | Feature freeze | | ~~2016-07-26~~ 2016-08-16 2016-08-02 | Beta, Branches created | | ~~2016-08-02~~ 2016-08-23 2016-08-09 | Release candidate | | ~~2016-08-09~~ 2016-08-30 2016-08-16 | GA Release | 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 blocking issues are resolved and 2.10 is unblocked. The schedule above is tentative, Beta and may still change depending on the results of integration testing. subsequent releases will be arriving one week later than planned. # Pulp 2.11 Release Schedule **Due to the delays in the 2.10 mentioned above, it is likely that the 2.11 release will be delayed.** | | | | ---------- | ---------------------------- | | 2016-08-09 | 2.10 GA Planned Release Date | | 2016-08-30 | Feature freeze | | 2016-09-06 | Beta, Branches created | | 2016-09-13 | Release candidate | | 2016-09-20 | GA Release | # Future Releases 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. # Definitions **Beta** - All bug fixes that need to be in the release are complete. Dev believes the release is ready. **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. **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. **Generally Available** (GA) - Release is generally available in the stable repositories. **Dev branch** - Branch created for Z (bugfix) release code changes related to a Generally Available Y release. # Y Release Cadence The Y release cycle begins on the day of the previous GA Y release. - week 0: (Y-1) Previous Y Generally Available Release - week 3: Feature Freeze - week 4: Beta Y release - dev branch created for this Y Release - build system adapted to build from dev branch - master branch now tracks development for next Y release - beta is built from dev branch - week 5: Y Release Candidate - week 6: Generally Available Y Release # Z Release Cadence 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. - week 0: (Z-1) Previous Z GA Release - week 1: Beta Z Release - week 2: GA Z Release Z releases are released as often as possible based on this schedule.
.