Skip to content

Describe release process - #114

Merged
Gerrrr merged 2 commits into
masterfrom
release-process
Dec 22, 2025
Merged

Gerrrr merged 2 commits into
masterfrom
release-process

Conversation

@Gerrrr

@Gerrrr Gerrrr commented Dec 15, 2025

Copy link
Copy Markdown
Contributor

This PR solves #74 and hopefully motivates another PMC member to do the next release :)

@henrikingo henrikingo left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Alex! This is a huge and well executed effort and I'd say we are now in a position to produce many more Otava releases under the ASF process for years to come <3

+1 from me but I'll leave it for you to do the merge if you want to do any final edits still.

Comment thread docs/RELEASE.md Outdated
The Otava community treats releases with great importance. They are a public face of the project and most users interact with the project only through the releases. Releases are signed off by the entire Otava community in a public vote.
Each release is executed by a Release Manager, who is selected/proposed by the Otava PMC members. This document describes the process that the Release Manager follows to perform a release. Any changes to this process should be discussed and adopted on the [dev@otava.apache.org](mailto:dev@otava.apache.org) mailing list.

Please remember that publishing software has legal consequences. This guide complements the foundation-wide [Product Release Policy](https://www.apache.org/dev/release.html) and [Release Distribution Policy](https://www.apache.org/dev/release-distribution).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would maybe soften but also broaden the first sentence. (But maybe as you now live in an English speaking country, I'll leave final judgement to you):

Please remember, that the act of publishing software has both legal and policy significance.

Comment thread docs/RELEASE.md Outdated
1. Decide to release
2. Prepare for the release
3. Build a release candidate
4. Vote on the release candidate

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

4b) While we are in the ASF incubator program, voting has 2 phases: On the Otava project mailing list, then formally on the Incubator project list.

@henrikingo

Copy link
Copy Markdown
Contributor

I was thinking that as soon as we get our story straight on what we expect from the CLI vs command line, we could do a new release with the new python versions + new algorithm implementation pretty soon.

@Gerrrr

Gerrrr commented Dec 22, 2025

Copy link
Copy Markdown
Contributor Author

Yeah, in the next couple of days, I plan to start a mailing thread to scope remaining work for 1.0.0 release.

@Gerrrr
Gerrrr merged commit 3b3d59a into master Dec 22, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants