Re: Next release(s)

On Mon, Feb 6, 2023 at 9:11 AM Andres Almiray wrote: > A couple of inline comments but thanks for the pointers. I went ahead > without making changes for the current releases. :-) > > > Right. It was too close time-wise to adjust the release process with > JReleaser. Once the current release is o

Re: Next release(s)

A couple of inline comments but thanks for the pointers. I went ahead without making changes for the current releases. :-)Right. It was too close time-wise to adjust the release process with JReleaser. Once the current release is out we can have another look. Later Groovy versions (4+) are reproduc

Re: Next release(s)

A couple of inline comments but thanks for the pointers. I went ahead without making changes for the current releases. :-) On Sat, Feb 4, 2023 at 1:31 AM Andres Almiray wrote: > Thanks Paul, > > I guess I'll have to create a map of tasks, their dependencies, and their > behavior to have a better

Re: Next release(s)

Thanks Paul, I guess I'll have to create a map of tasks, their dependencies, and their behavior to have a better understanding of the release process. I can see that files are uploaded to an Artifactory instance - https://jreleaser.org/guide/latest/reference/upload/artifactory.html for Zips - h

Re: Next release(s)

As long as we use the release manager's Apache email address, the current announcer sounds like it will be fine. We currently wait until artifacts have synced with Maven Central before sending the email. Currently that's a manual step. See adhoc.gradle#checkMavenStatus. It wouldn't be hard to tweak

Re: Next release(s)

Hi Paul, Great. Thank you for that explanation. Saved me a lot of time searching :D At the moment the SMTP announcer can only configure a single sender, single message, multiple recipients. I could imagine the following scenarios: 1. multiple senders, same message 2. single sender, multiple mess

Re: Next release(s)

Hi Andres, It's been on my TODO list to incorporate JReleaser where we can but I haven't found the cycles to date. Your suggestion is certainly a possibility! The release process (two phases to allow for ASF voting) is driven by the Gradle scripts in: https://github.com/apache/groovy-release/ T

Re: Next release(s)

Hi Paul, Though not strictly related to new features, what are your thoughts on configuring JReleaser for posting announcements to all supported distribution channels? The tool can post to Twitter, Mastodon, and send an e-mail via its SMTP announcers. If it makes sense, I can craft a PR which cou

Re: next release(s)

Hi Paul, I'm trying to release 2.6.0-alpha-1 and wish everything would be OK :) P.S. building and uploading artifacts cost me 6+ hours (about 20KB/s), OMG... Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/next-release-s-tp5742268p5742700.html Se

Re: next release(s)

Hi Daniel, I will contact you offline with some more details. The main thing is to check out the release repo: https://github.com/apache/groovy-release You will also need to generate yourself a key and add it to the KEYS files: https://dist.apache.org/repos/dist/dev/groovy/KEYS https://dist.apac

Re: next release(s)

Hi Paul, I think I can set aside some time to release 3.0.0-alpha-1. Is there any document to guide me to complete it? Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/next-release-s-tp5742268p5742605.html Sent from the Groovy Dev mailing