Content
View differences
Updated by Christophe Bliard almost 2 years ago
**Prerequisites**
* Devkit [https://github.com/opf/openproject-devkit](https://github.com/opf/openproject-devkit)
**Steps**
For example, you're trying to release OpenProject 13.0. You will need to create a release branch `release/13.0` from current `dev` branch. Assuming that dev branch is at 13.0.0 version, the following command.
`./bin/opdev create-release-branch`
will create release/13.0 branches in the repositories [opf/openproject](https://github.com/opf/openproject), [opf/openproject-deutsche\_bahn](https://github.com/opf/openproject-deutsche_bahn), [opf/openproject-open\_desk](https://github.com/opf/openproject-open_desk), and [opf/saas-openproject](https://github.com/opf/saas-openproject).
Remember to use `--push` to actually push the release branch once you're ready.
You might be likely to create the release branch days before the actual release. Ensure that the release branch exists before continuing with the release, since it is the source of the release that gets built.
**Checklist**
* [x] [ ] Bump `dev` branch afterwards to the next minor/major release in file `lib/open_project/version.rb` (to prevent invalid translations on crowdin)
* [x] [ ] Inform devs and writers that all documentation and bugs now need to be made against the new release branch in Element #general room
* [x] [ ] Update static-website **stage** action to point to new release branch following instructions in [https://github.com/opf/openproject-website/blob/release/documentation/DOCS.md](https://github.com/opf/openproject-website/blob/release/documentation/DOCS.md)
* [x] [ ] Update the flavours repository workflow to deploy stage using the new branch
* [x] [ ] [https://github.com/opf/openproject-flavours/blob/dev/.github/workflows/ci.yml#L27](https://github.com/opf/openproject-flavours/blob/dev/.github/workflows/ci.yml#L27)
* [ ] For a major release: [https://github.com/opf/openproject-flavours/blob/dev/.github/workflows/ci.yml#L33](https://github.com/opf/openproject-flavours/blob/dev/.github/workflows/ci.yml#L33)
* [x] [ ] Update the [monitoring page badges](https://github.com/opf/monitoring) to point to the new branch by updating https://github.com/opf/monitoring/blob/main/README.md
* [x] [ ] Alter the release branch used to deploy to the stage environment: [https://ci.openproject.com/view/CONVOX-2-STAGE/job/convox-stage-deploy-shards/](https://ci.openproject.com/view/CONVOX-2-STAGE/job/convox-stage-deploy-shards/)<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/102770/content">
* Devkit [https://github.com/opf/openproject-devkit](https://github.com/opf/openproject-devkit)
**Steps**
For example, you're trying to release OpenProject 13.0. You will need to create a release branch `release/13.0` from current `dev` branch. Assuming that dev branch is at 13.0.0 version, the following command.
`./bin/opdev create-release-branch`
will create release/13.0 branches in the repositories [opf/openproject](https://github.com/opf/openproject), [opf/openproject-deutsche\_bahn](https://github.com/opf/openproject-deutsche_bahn), [opf/openproject-open\_desk](https://github.com/opf/openproject-open_desk), and [opf/saas-openproject](https://github.com/opf/saas-openproject).
Remember to use `--push` to actually push the release branch once you're ready.
You might be likely to create the release branch days before the actual release. Ensure that the release branch exists before continuing with the release, since it is the source of the release that gets built.
**Checklist**
* [x]
* [x]
* [x]
* [x]
* [x]
* [ ] For a major release: [https://github.com/opf/openproject-flavours/blob/dev/.github/workflows/ci.yml#L33](https://github.com/opf/openproject-flavours/blob/dev/.github/workflows/ci.yml#L33)
* [x]
* [x]