Hello Everyone, The following draft release has been generated with github actions: https://github.com/apache/incubator-baremaps/releases/tag/untagged-4d07860016b500637021
We have two distributions (source and binary) created with the maven assembly plugin. The checksums and signatures are generated by the CI. For now, the PGP signatures are computed with the PGP key used to sign the maven artifacts. The release action is located here: https://github.com/apache/incubator-baremaps/blob/cd0a1fdb7c7c29a6f41d1f299239cb61580b3036/.github/workflows/release.yml#L23 In order to publish a new release, the release manager would have to perform the following steps: 1) create a branch for the release 2) execute the mvn release:prepare command in this branch 3) check that the release action completes on github and produces a draft of the release 4) generate and edit the release notes on github 5) ask the mailing list to vote for the release 7) if the vote passes, merge the release branch into main and publish the release What do you think about this process? Do not hesitate to share your thoughts. Best, Bertil
signature.asc
Description: Message signed with OpenPGP
