-
Notifications
You must be signed in to change notification settings - Fork 221
Release process
Ferenc Erki edited this page Mar 5, 2020
·
9 revisions
- Prepare the release notes for the website
- base it on the changelog, following previous release notes as template
- push it to the website repo, open a PR, and wait for CI/human feedback with the release note
- prepare a news post too, following previous release posts as template
- Release with
dzil release
- Commit all generated changes with the commit message (
Release 1.8.2
) - Tag the release commit with the version (
git tag 1.8.2
)
- Tag the release commit with the version (
git tag 1.8.0
) - Build the release with
dzil build
.- force next version with the
V
environment variable:V=1.2.3 dzil build
- use
_0x
suffix and--trial
for development releases:V=1.8.0_01 dzil build --trial
- force next version with the
- Check the build contents as needed
- When satisfied, upload tarball to PAUSE
- Push the tag to master branch
- Publish the release notes to the website
- Announce new release on the various channels
- mailing list
- IRC