Release Schedule » History » Revision 24
Revision 23 (semyers, 09/16/2016 07:28 PM) → Revision 24/86 (semyers, 10/27/2016 05:42 PM)
# Pulp 2.11 Release Schedule The Pulp 2.11 Release date has not been decided. Once decided, this page will be updated, and the release will follow the normal release schedule starting at the feature freeze (see below). # 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. A 2.12 release is expected but a date has not yet been set for this release. # Release Stages Definitions **Beta** - All bug fixes that need to be in the release are complete. Dev believes the release is complete and ready ready. **Feature Freeze** - No new features allowed after this date. Though exceptions can be made for testing. Any bug fixes related work waiting on review, the submitter should attempt to this release are still acceptable. have work reviewed and merged before the freeze date. **Release Candidate** (RC) - Only QE has performed their testing and is satisfied to release. No new bug fixes related to regressions, upgrade failures, after this point. Regressions or similar severity other urgent bug fixes will be handled case by case. There are accepted at this point. no release candidates for Z releases. **Generally Available** (GA) - Release is generally available in the stable repositories. ## Release Stage Conditions Releases spend a minimum time of one week in a given **Dev branch** - Branch created for Z (bugfix) release stage. Subsequent releases in a given stage do not "reset the clock" on this waiting period. Care is taken code changes related to verify release-breaking bugs prior to advancing to the next release stage, which usually adds a few days to the release cycle, preventing "rapid-fire" releases. ### Z Release Beta There are no release candidates for Z releases. Z releases advance directly to GA after testing reveals no new blocking issues, and have passed acceptance testing by QE (including upgrade testing). ### Generally Available Y Release Beta release. Y releases advance to RC after testing reveals no new blocking issues, and have passed acceptance testing by QE (not including upgrade testing). ### Y Release RC This release stage cannot advance to GA until the upgrade path from previous versions of pulp is confirmed to be working. # Y Release Cadence Due to the unpredictable timeline of the release schedule once a Beta is released, the The Y release cycle begins on the day of the previous **Beta** GA Y release. While unpredictable, the 12-week period between beta releases should be more than adequate to get that release Generally Available and still allow a few weeks before the next Beta is announced. - week 0: (Y-1 Release) (Y-1) Previous Y release cycle begins with a Beta Generally Available Release - week 12: (Y Release) 3: Feature Freeze - week 4: Beta Y release cycle begins with a Beta Release - dev branch created for this Y Release, preventing the addition of new features. 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 12+1?: 5: Y release advances through Beta stage to RC as stage conditions are met. Release schedule is no longer time-based. Candidate - week 12+2?: 6: Generally Available Y release advances through RC phase to GA as stage conditions are met. Release This release cadence was introduced to coincide with the release of the 2.11.0 Beta on 2016/10/25. If desired, the previous Y release cadence can be seen in the history of this wiki document. # 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, but are subject to upgrade testing which often extends the beta period beyond a week. # Version Numbering To the best of our ability, our releases adhere to semantic versioning. The releases in this document correspond to releases that increment a given release component (Y or Z) as defined by semantic versioning: http://semver.org/#spec-item-2 In short, a "Z Release" increments the "Z" release component (e.g. 1.0.0 -\> 1.0.1), and indicates no new features; only bug and security fixes have taken place. A "Y Release" increments the "Y" release component (e.g. 1.0.0 -\> 1.1.0), and indicates that new features have been introduced, but backward-incompatible API changes have not taken place. "X" Releases are not covered by this document. At the moment, they are rare enough as to be handled case-by-case. The next X release, Pulp 3, is currently being actively discussed on the pulp-dev mailing list. If you're interested in participating, go here to subscribe: https://www.redhat.com/mailman/listinfo/pulp-dev schedule.
.