Thanks, James! I will do that. Paul had also offered me some insight over Slack, so I'm less blocked, just a bit time constrained now. 😅
I'll be in touch. On Thu, Jul 17, 2025 at 7:31 PM James Daugherty <jdaughe...@apache.org> wrote: > Hi Jonny, > > I recently went through this with Grails. Are you building Geb all > locally? Do you have any interest in setting up github actions to assist > in your release? If you do, reach out to me on the Groovy Slack, ASF > Slack, or via my email? I have previously offered my help to Paul on what > I learned using CI to help perform the release. > > -James > > On 2025/07/16 13:29:58 Jonny wrote: > > I need some help and guidance on getting the first Apache release for Geb > > done and out the door. I think my message on the Geb mailing list > > <https://lists.apache.org/thread/9hpgcsvq92wdd8oj4okh0gco4q9f719h> > didn't > > seem to reach anyone, so I'll keep this short and to the point. > > > > First, what steps do I need to take to be named the release manager for > Geb? > > > > Second, where should I upload the artifacts (jar file and crypto key)? I > > assume it would be to https://dist.apache.org/repos/dist/dev/groovy/geb/ > , > > but I'm a little hazy on how subproject status works. > > > > I should be able to generate the sha-512 crypto keys > > <https://infra.apache.org/release-signing.html> to sign the release and > > upload it to keys.openpgp.org, but is that all there is to it? > > > > Are there any hygiene rules around where release jars get created? For > > example, should they be generated on the Apache Jenkins instance? > > > > If anyone can point me to how the Groovy repo answers the above questions > > and just say, "Follow that example," that would help. > > > > Best, > > > > Jonny Carter > > >
