Hi folks, I might try to do a 4.0.9 late this week or early next week. This
is mostly to incorporate some OSGi fixes. It turns out all Groovy 4
releases until now have a minor glitch for certain OSGi environments.
I might also do a bump on 3_0_X if I have time.
It's time to get in any desired fix
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
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
Paul,
I'd like to get a fix in for GROOVY-10911 before the deadline. I haven't
gotten to it yet, but the submitter has now provided a recreation script, so it
should take more than another day.
From: Paul King
Sent: Wednesday, February 1, 2023 6:43 AM
To: Groovy_Developers
Subject: [EXT] Ne
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
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
paulk-asert merged PR #42:
URL: https://github.com/apache/groovy-website/pull/42
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@groovy.
