This is an automated email from the ASF dual-hosted git repository.
jamesfredley pushed a commit to branch 7.0.x
in repository https://gitbox.apache.org/repos/asf/grails-core.git
The following commit(s) were added to refs/heads/7.0.x by this push:
new 977858fa7f Revise ASF reporter instructions in RELEASE.md
977858fa7f is described below
commit 977858fa7fdf4f8681aedb3ba9cea6a5594fd658
Author: James Fredley <[email protected]>
AuthorDate: Sun Oct 19 15:46:08 2025 -0400
Revise ASF reporter instructions in RELEASE.md
Updated instructions for the ASF reporter and removed note about Grails
podling.
---
RELEASE.md | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/RELEASE.md b/RELEASE.md
index 0a88afa85e..c8596aa018 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -286,13 +286,11 @@ an example call to the checked in script to move the
distributions.
### Update ASF Reporter
After moving the distributions, you will receive an email from the ASF
reporter. Click the link in the email to mark the
-release as published. The `release` job in the `Release` workflow has a step
to remind you of this.
+release as published or go to
https://reporter.apache.org/addrelease.html?grails. The `release` job in the
`Release` workflow has a step to remind you of this.
For example, if the release is out of core with version `7.0.0-M4`, then the
release name with be `CORE-7.0.0-M4`. Enter
the date you moved the distribution artifacts and report the release.
-NOTE: Grails as a podling, cannot currently do this.
-
### Deploy grails-forge so the release is accessible on start.grails.org
On the `grails-core` repository, using the release tag, deploy the
grails-forge-web-netty docker container to Google Cloud Run using one of the
GCP Deploy actions.
