Pulp

# Pulp 2.9 Release Schedule

|                            |                         |                                                                   |

| -------------------------- | ----------------------- | ----------------------------------------------------------------- |

| 2016-06-07                 | 2.9.0 Feature freeze    | Only bug fixes after this                                         |

| ~~2016-06-14~~ 2016-06-21  | 2.9.0 Beta              | dev branches created: Build system adapted to build from branches |

| ~~2016-06-21~~ **BLOCKED** | 2.9.0 Release candidate | Final Freeze                                                      |

| ~~2016-06-28~~ ?           | 2.9.0 GA Release        | Pulp 2.9 is Generally Available                                   |

2.9.0 Blockers:

  - https://pulp.plan.io/issues/2035

  - https://pulp.plan.io/issues/2037

Build infrastructure problems and a blocking bug pushed the beta release and all subsequent releases of 2.9 back one week.  

These delays have not affected the 2.10 release timeline.

# Pulp 2.10 Release Schedule

|            |                        |

| ---------- | ---------------------- |

| 2016-06-28 | Previous Y GA Release  |

| 2016-07-19 | Feature freeze         |

| 2016-07-26 | Beta, Branches created |

| 2016-08-02 | Release candidate      |

| 2016-08-09 | GA Release             |

# 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.