search

apache / maven-mvnd

Apache Maven Daemon
https://maven.apache.org/
Apache License 2.0
2.91k stars 207 forks source link

Release process #623

Open gnodet opened 2 years ago

gnodet commented 2 years ago

I've reverted some usage of jreleaser to actually cut the release and got back to a simple script which triggers the workflow after having updated everything locally (it seems the ASF will not allow us to use GitHub actions which will commit/tag automatically).

So this is the first phase of our release process, which is mostly about generating the source distribution (the official thing that is being released from an ASF pov) and the convenience binaries. The output will be something like https://github.com/apache/maven-mvnd/releases/tag/0.8.0

Now, once the vote on the ASF mailing list passes, we need to continue the release process and proceeded to

@aalmiray given we can't really use actions, is there anything jreleaser can help us with ? I guess I'll have to use a script that the release manager will have to run anyway, because signing the releases involves using its private key which can't be done on the GitHub hardware

aalmiray commented 2 years ago

Understood. The use of jreleaser/release-action is just a convenience when running inside a GitHub workflow. The JReleaser CLI may be used without such action, likely triggered by a script that the release admin has control over.

davsclaus commented 2 years ago

@gnodet I cannot find where you can download mvnd 0.8.0 release binaries for linux / mac etc anymore. The link you pointed to at ASF is empty. And they are no longer here on github -> releases page (last is 0.7.1).

Ah your link is wrong - I noticed it was 'dev' and the release is here https://dist.apache.org/repos/dist/release/maven/mvnd/0.8.0/

ppalaga commented 2 years ago

0.8.0 artifacts are here https://github.com/apache/maven-mvnd/releases/tag/untagged-bf2dbba4d6b46cb85615 @gnodet is there any reason why the release is still marked as draft?