henrikingo commented on PR #159: URL: https://github.com/apache/otava/pull/159#issuecomment-4472446191
Follow-up activities to the release: * This PR: Several additions and clarifications to docs/RELEASE.md * Unless someone objects, I will move the previous releases 0.6.0, 0.7.0 and 0.7.1 from https://dist.apache.org/repos/dist/dev/incubator/otava/ to https://dist.apache.org/repos/dist/release/incubator/otava/ * Website, one remaining fix: The "all releases" part of https://otava.apache.org/docs/download should point to URLs that start with archive.apache.org or in any case never to https://dist.apache.org/repos/dist/dev/incubator/otava/ * IMO docker builds should also be published somewhere before voting. Proposal beloiw. The above should fix everything that came up during the voting and review on the Incubator list. But one last comment is that this process has way too many manual steps. It is almost 2 days of work (for a first timer anyway) and very error prone due to the complexity. So I would like to propose as follow-up work that we automate a large part of this in Github CI. Specifically, the creation of source tar, pypi tar and whl, and docker image should be running in CI anyway. If the CI detects that user pushed a tag that has the form `x.y.z-incubating-rcN` then the resulting artifacts will also be attached to the result of the workflow. The release managers job is then just to download and carefully test and review these files, sign them, upload to dist.apache.org/.../dev/ and start the voting. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
