Merge pull request #1390 from p12tic/new-releases-numbers

Update releasing procedure for release numbers and add missing details
This commit is contained in:
Povilas Kanapickas 2021-11-05 14:43:50 +02:00 committed by GitHub
commit 4e082404f1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 23 additions and 4 deletions

View File

@ -30,6 +30,8 @@ body:
- v2.3.2-alpha - v2.3.2-alpha
- v2.3.2 - v2.3.2
- v2.3.3 - v2.3.3
- v2.3.4
- v2.4.0
- From Git HEAD or commit (specify below) - From Git HEAD or commit (specify below)
validations: validations:
required: true required: true

View File

@ -27,11 +27,28 @@ Check `newsfragments` directory for any forgotten release notes
Step 3: Merge the release notes PR Step 3: Merge the release notes PR
---------------------------------- ----------------------------------
Step 4: Push git tag Step 4: Bump the version number
-------------------- -------------------------------
Pull the merge commit created on the `master` branch during the step 2. Pull the merge commit created on the `master` branch during the step 2.
Edit the following files and update the version numbers:
- `Build.properties`
- `cmake/Version.cmake`
- `doc/barrierc.1`
- `doc/barriers.1`
- `.github/ISSUE_TEMPLATE/bug_report.yml`
Commit to the release branch with the following message `Barrier x.y.z`.
Push the commit:
git push origin master
Step 5: Push git tag
--------------------
Create a tag: Create a tag:
git tag -s v${VERSION} -m v${VERSION} git tag -s v${VERSION} -m v${VERSION}
@ -41,7 +58,7 @@ Push the tag:
git push origin master --tags git push origin master --tags
Step 5: Draft a new release on Github Step 6: Draft a new release on Github
------------------------------------- -------------------------------------
Go to https://github.com/buildbot/buildbot/releases and draft a new release. Go to https://github.com/buildbot/buildbot/releases and draft a new release.
@ -53,7 +70,7 @@ Use the release notes generated by the `towncrier` tool as the description of th
Upload the artifacts created by Azure pipelines as the binaries of the release. The following Upload the artifacts created by Azure pipelines as the binaries of the release. The following
artifacts should be uploaded to Github: artifacts should be uploaded to Github:
- the Barrier-X.Y.Z-release.dmg created by the oldest Mac OS task (artifact name is - the Barrier-X.Y.Z-release.dmg created by the newest Mac OS task (artifact name is
"Mac Release Disk Image and App XYZ"). "Mac Release Disk Image and App XYZ").
- the BarrierSetup-X.Y.Z-release.exe (artifact name is Windows Release Installer). - the BarrierSetup-X.Y.Z-release.exe (artifact name is Windows Release Installer).