This is an automated email from the ASF dual-hosted git repository.
paulk pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/groovy-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 96bcdea fix links
96bcdea is described below
commit 96bcdead45f533aac2f41e4d9af92e6173a07613
Author: Paul King <[email protected]>
AuthorDate: Wed Feb 26 21:28:12 2025 +1000
fix links
---
site/src/site/wiki/groovy-release-discussion.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/site/src/site/wiki/groovy-release-discussion.adoc
b/site/src/site/wiki/groovy-release-discussion.adoc
index eec7331..39a625a 100644
--- a/site/src/site/wiki/groovy-release-discussion.adoc
+++ b/site/src/site/wiki/groovy-release-discussion.adoc
@@ -43,7 +43,7 @@ But in addition to those benefits, it's the release process
itself which greatly
* the deployment infrastructure moved from Codehaus to {bintray} and
http://www.jfrog.com/open-source/[Artifactory]
* several build plans are dedicated to builds and releases:
-** the
http://ci.groovy-lang.org/viewType.html?buildTypeId=Groovy_BintrayIntegration_UploadSnapshots&guest=1[snapshot
upload] plan builds Groovy from sources and deploys the artifacts to the
http://oss.jfrog.org/oss-snapshot-local/org/codehaus/groovy/[OSS Artifactory
Snapshot Repository].
+** the
http://ci.groovy-lang.org/viewType.html?buildTypeId=Groovy_BintrayIntegration_UploadSnapshots&guest=1[snapshot
upload] plan builds Groovy from sources and deploys the artifacts to the
\http://oss.jfrog.org/oss-snapshot-local/org/codehaus/groovy/ [OSS Artifactory
Snapshot Repository legacy URL].
** the
http://ci.groovy-lang.org/viewType.html?buildTypeId=Groovy_BintrayIntegration_ReleasePlan&guest=1[release
plan] allows a release manager to release a new version of Groovy directly
from the CI server
** the
http://ci.groovy-lang.org/viewType.html?buildTypeId=Groovy_BintrayIntegration_GvmBroadcast[GVM
broadcast] plan allows us to announce a new release of Groovy to
\http://gvmtool.net/ (obsolete - now SDKMAN) and its
https://twitter.com/gvmtool[Twitter account] directly from the CI server
** the
http://ci.groovy-lang.org/viewType.html?buildTypeId=Groovy_BintrayIntegration_GvmMakeDefault[GVM
default] plan allows us to notify GVM that a specific Groovy version is the
new default version, directly from the CI server