There are a few things to think about. The ASF has official releases which are voted on, but we also support community artifacts which don't need a vote. This is how the current Windows installer is done. Keegan does a great job with this, but long-term we might want to even reduce his burden and automate the release if we can. I think the same would apply to snaps - in the first instance, we'd do them outside the release process as a follow-on task, but eventually we'd probably like to integrate them, and we can decide at that time whether we vote on them or what path we go down in terms of ASF process/policy compliance.
So, we can do the steps manually (which is what I used to do), or hook into the existing (or future) release process. Currently, we release using the Gradle scripts from the groovy-release repo. In the short term, we could add another task in the adhoc script. Such a task could still be run outside the release process or eventually added to it. I am hoping to convert all of this to follow what Grails has done using GitHub actions. Once that is done, that would be the natural home. Once I get the next round of releases out, I'll try to refresh my knowledge of what I used to do. Cheers, Paul. On Tue, Jul 28, 2026 at 3:19 PM Balachandran Sivakumar <[email protected]> wrote: > > Hi Paul, > > Thanks for the support - Is there a separate repo for snap that I > can submit PRs against? Or, do we maintain that in the main repo, under > a snap folder, such that when a tag is applied, it generates the snap > from the zip build and pushes to snap store? Thanks > > > Thank you, > Balachandran Sivakumar > > On 28/07/26 00:48, Paul King wrote: > > That would be cool. > > > > On Tue, Jul 28, 2026 at 5:02 AM Balachandran Sivakumar > > <[email protected]> wrote: > >> Hi All, > >> > >> When trying something with snap on Ubuntu, I noticed that Groovy > >> has a snap package that is not actively maintained. I am not sure who > >> the current maintainer of that is, but it seems to be owned by the > >> official Apache Groovy community [1] > >> > >> If there are no objections from the current maintainer(s), and the > >> community/ASF has no objections to maintaining the snap package, I would > >> like to help/contribute maintain the snap package. Thanks > >> > >> [1] Groovy snap page - https://snapcraft.io/groovy > >> > >> -- > >> Thank you, > >> Balachandran Sivakumar > >>
