![]() Note: since one of the tools (rpm-s3 on CentOS) doesn't support AWS GITHUB_AUTHORIZATION_TOKEN, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, On each machine you'll be releasing from, set environment variables: With tag and name vX.Y.Z (where X.Y.Z is the stack package's version), targeting the That allows you to iterate on the release process while building a Tree containing the script will be used to build the stack code in the currentĭirectory. if you have stack1Īnd stack2 trees, and run cd stack1. Remove unsupported/obsolete distribution versions from the release process.įor requirements to perform the release, and more details about the tool.Ī note about the etc/scripts/*-releases.sh scripts: if you run them from aĭifferent working tree than the scripts themselves (e.g.Check that no new entries need to be added to. ![]() github/ISSUE_TEMPLATE.md to point at the new version. Ensure all documentation pages listed in mkdocs.yaml.Look for any links to "latest" documentation, replace with version tag."obvious" version in sequence (if doing a non-obvious jump), and Search for old Stack version, unstable stack version, and the next.Review documentation for any changes that need to be made.Check for any entries that snuck into the previous version's changesĭue to merges ( git diff origin/stable HEAD ChangeLog.md).Check for any important changes that missed getting an entry inĬhangelog ( git log origin/stable.HEAD).Changelog: add new "unreleased changes" section.stack.cabal: bump version number to unstable (odd third component).Cut a release candidate branch rc/vX.Y.Z from master.ChangeLog: rename the "Unreleased changes" section to the new version.stack.cabal: bump the version number to release (even third. ![]() Thorough test for every platform/variant prior to uploading, so this is just a The actual release script will perform a more Stack install -pedantic & stack test -pedantic -flag
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |