You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by gg...@apache.org on 2025/01/12 20:08:43 UTC
(commons-release-plugin) branch master updated (599c7c5 -> 04ccfa5)
This is an automated email from the ASF dual-hosted git repository.
ggregory pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/commons-release-plugin.git
from 599c7c5 Better text for release notes
new 5fa0c08 Remove mention of CLIRR, it's obsolete
new 04ccfa5 Update vote template with reproducible build information
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../commons-xdoc-templates/vote-txt-template.txt | 41 +++++++++++++---------
1 file changed, 24 insertions(+), 17 deletions(-)
(commons-release-plugin) 02/02: Update vote template with reproducible build information
Posted by gg...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
ggregory pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-release-plugin.git
commit 04ccfa5a53238eb34890ccde11440c16ddf9eb5b
Author: Gary D. Gregory <ga...@gmail.com>
AuthorDate: Sun Jan 12 15:08:37 2025 -0500
Update vote template with reproducible build information
---
.../commons-xdoc-templates/vote-txt-template.txt | 26 ++++++++++++++++++----
1 file changed, 22 insertions(+), 4 deletions(-)
diff --git a/src/main/resources/commons-xdoc-templates/vote-txt-template.txt b/src/main/resources/commons-xdoc-templates/vote-txt-template.txt
index fa93b8d..d002888 100755
--- a/src/main/resources/commons-xdoc-templates/vote-txt-template.txt
+++ b/src/main/resources/commons-xdoc-templates/vote-txt-template.txt
@@ -94,29 +94,39 @@ Requirements: Git, Java, and Maven.
You can validate a release from a release candidate (RC) tag as follows.
-1a) Clone and checkout the RC tag
+1a) Download and decompress the source archive from:
+
+@DISTURL@/source
+
+1b) Check out the RC tag from git (optional)
+
+This is optional, as a reviewer must check source distributions as a minimum.
git clone https://gitbox.apache.org/repos/asf/commons-@ID@.git --branch @TAGNAME@ @TAGNAME@
cd @TAGNAME@
-1b) Download and unpack the source archive from:
+2) Checking the build
-@DISTURL@/source
+All components should include a default Maven goal, such that you can run 'mvn' from the command line by itself.
2) Check Apache licenses
This step is not required if the site includes a RAT report page which you then must check.
+This check should be included in the default Maven build, but you can check it with:
mvn apache-rat:check
3) Check binary compatibility
This step is not required if the site includes a JApiCmp report page which you then must check.
+This check should be included in the default Maven build, but you can check it with:
-mvn install -DskipTests -P japicmp japicmp:cmp
+mvn verify -DskipTests -P japicmp japicmp:cmp
4) Build the package
+This check should be included in the default Maven build, but you can check it with:
+
mvn -V clean package
You can record the Maven and Java version produced by -V in your VOTE reply.
@@ -124,6 +134,14 @@ To gather OS information from a command line:
Windows: ver
Linux: uname -a
+4b) Check reproducibility
+
+To check that a build is reproducible, run:
+
+mvn clean verify artifact:compare -DskipTests -Dreference.repo=https://repository.apache.org/content/repositories/staging/ '-Dbuildinfo.ignore=*/*.spdx.json'
+
+Note that this excludes SPDX files from the check.
+
5) Build the site for a single module project
Note: Some plugins require the components to be installed instead of packaged.
(commons-release-plugin) 01/02: Remove mention of CLIRR, it's obsolete
Posted by gg...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
ggregory pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-release-plugin.git
commit 5fa0c087a7a877cf5db1890a9aeba194b8bccf0c
Author: Gary D. Gregory <ga...@gmail.com>
AuthorDate: Sun Jan 12 14:54:18 2025 -0500
Remove mention of CLIRR, it's obsolete
---
.../commons-xdoc-templates/vote-txt-template.txt | 15 ++-------------
1 file changed, 2 insertions(+), 13 deletions(-)
diff --git a/src/main/resources/commons-xdoc-templates/vote-txt-template.txt b/src/main/resources/commons-xdoc-templates/vote-txt-template.txt
index 0cdbae9..fa93b8d 100755
--- a/src/main/resources/commons-xdoc-templates/vote-txt-template.txt
+++ b/src/main/resources/commons-xdoc-templates/vote-txt-template.txt
@@ -36,7 +36,7 @@ These are the artifacts and their hashes:
@SHA512LIST@
-I have tested this with ***'mvn clean install site'*** using:
+I have tested this with 'mvn' and 'mvn clean install site' using:
***
Use the output from "mvn -version" for each combination you tested.
Windows: ver
@@ -51,9 +51,6 @@ Site:
@SITEURL@/index.html
(note some *relative* links are broken and the @VERSION@ directories are not yet created - these will be OK once the site is deployed.)
-*** CLIRR Report (compared to @BC@):
- @SITEURL@/clirr-report.html
-
*** JApiCmp Report (compared to @BC@):
@SITEURL@/japicmp.html
@@ -93,7 +90,7 @@ Validating a release candidate
These guidelines are NOT complete.
-Requirements: Git, Java, Maven.
+Requirements: Git, Java, and Maven.
You can validate a release from a release candidate (RC) tag as follows.
@@ -114,14 +111,6 @@ mvn apache-rat:check
3) Check binary compatibility
-Older components still use Apache Clirr:
-
-This step is not required if the site includes a Clirr report page which you then must check.
-
-mvn clirr:check
-
-Newer components use JApiCmp with the japicmp Maven Profile:
-
This step is not required if the site includes a JApiCmp report page which you then must check.
mvn install -DskipTests -P japicmp japicmp:cmp