search

deis / workflow

The open source PaaS for Kubernetes.
https://deis.com/workflow/
MIT License
1.3k stars 181 forks source link

release-checklist: figure out how to avoid code freezes #233

Closed bacongobbler closed 8 years ago

bacongobbler commented 8 years ago

The current release workflow requires us to call a development "code freeze" for all pull requests until we're finished with a release. We should try and engineer a way to cut a release without needed to completely freeze all merges across the organization.

Joshua-Anderson commented 8 years ago

Could something like this possibly work?

When preparing to cut a release:

  1. Create a new RC branch
  2. Landings can continue on master and testing/QA can proceed on the RC branch.
  3. If bug is caught in the RC, a PR is sent to master, merged, and then cherry picked over to the RC branch.
bacongobbler commented 8 years ago

Yep! That's the exact process we thought of. This came out of our release retrospective this afternoon. The work that has yet to be done for this approach now is to get deisrel and deis-workflow-group to have the ability to cut charts from the latest commit on the RC branch, make the component jobs in jenkins build and deploy RC images from said branch, and update the release checklist with the new process. Right now it's more of a "discovery" phase to figure out what other tooling/work needs to be done in order to use this release process.

bacongobbler commented 8 years ago

we've long since implemented this