henrikingo opened a new issue, #51:
URL: https://github.com/apache/otava/issues/51
...continuing from #33 . It seems we completed all of those tasks, only to
discover an even longer TODO list:
1. Agree on the release version (0.6.0-incubating? I am using that as a
placeholder in other steps).
2. Update release name in pyproject.toml.
3. Update project description and authors in pyproject.toml.
4. Verify supported Python versions. Run tests and examples with Python
3.8+. Add a paragraph to README claiming that versions where tests passed
are supported.
5. Create source distribution via `poetry build`.
6. Sign the artifact `gpg --armor --output dist/<artifact>.asc --detach-sig
dist/<artifact>`.
7. Verify the checksum `sha512sum dist/<artifact> > dist/<artifact>.sha512`.
8. Test release candidate locally with `pip install`.
9. Upload project KEYS file. **Q:** How do we do that?
KEYS files are currently a file of concatenated Release Manager’s GPG
Public Signing Keys uploaded via svn here:
svn import
https://dist.apache.org/repos/dist/release/incubator/otava/KEYS -m "Update
Otava KEYS"
10. Upload Artifacts to Apache Dev Repo. **Q:** How do we do that?
You currently `svn co
[https://dist.apache.org/repos/dist/dev/incubator/otava/`](https://dist.apache.org/repos/dist/dev/incubator/otava/)
Then you add the release candidate files to that directory and then `svn ci
-m “Release Candidate Otava 0.6.0-incubating”`
These files should be name `apache-otava-0.6.0-incubating.*`
11. Call for PMC Vote. Send an email to the this mailing list with
thesubject "VOTE: Release Apache Otava 0.6.0-incubating" with the link to the
release candidate:
```
The Apache Otava project is pleased to announce that the
release candidate for version 0.6.0-incubating is ready.
The release candidate artifacts are available at:
????
SHA512: <checksum>
KEYS:https://downloads.apache.org/incubator/otava/KEYS
Please vote on releasing this candidate by replying with:
[ ] +1 Release this package
[ ] 0 No opinion
[ ] -1 Do not release (please provide reason)
This vote will be open for at least 72 hours.
```
12. Wait for the vote to pass, fix issues if any.
13. Call for IPMC Vote. Send an email to
[[email protected]](mailto:[email protected]) withthe
subject "[VOTE] [RESULT] Release Apache Otava 0.6.0-incubating". The
content should contain links to the vote result and the artifacts.
14. Wait for the vote to pass, fix issues if any.
15. Move the RC to the release directory. **Q:** How do we do that?17.
Publish Github release/tag.
You do an `svn mv` from
https://dist.apache.org/repos/dist/dev/incubator/otava/<artifacts>
To https://dist.apache.org/repos/dist/release/incubator/otava/
16. Upload the release to PyPI.
https://incubator.apache.org/guides/distribution.html#pypi
17. Henrik will organize a release party on Teams, to coincide with the next
point:
18. Announce the release on the mailing list by sending an email with
thesubject "[ANNOUNCE] Apache Otava 0.6.0-incubating released". Please note
that announcement emails must be text and not html.
19. Make social media noise.
20. Henrik will write a blog post looking back at the companies and
collagues that contributed over the years. Also I have a conference
presentation (paper, but not peer reviewed) that I will publish. It mainly
focuses on the performance improvements going from O(n3) to O(1) in 8 years.
21. Bump version in pyproject.toml for the next release.
--
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]
