This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git
The following commit(s) were added to refs/heads/master by this push:
new 4a9d2967 improve RB instructions during votes
4a9d2967 is described below
commit 4a9d29670d6d1998a7f461f8492ef2391a36ac11
Author: Hervé Boutemy <hbout...@apache.org>
AuthorDate: Wed Mar 19 08:37:28 2025 +0100
improve RB instructions during votes
---
.../release/maven-project-release-procedure.apt | 20 +++++++-------------
.../guides/development/guide-testing-releases.apt | 9 ++++++++-
2 files changed, 15 insertions(+), 14 deletions(-)
diff --git a/content/apt/developers/release/maven-project-release-procedure.apt
b/content/apt/developers/release/maven-project-release-procedure.apt
index 80007ee3..042a507b 100644
--- a/content/apt/developers/release/maven-project-release-procedure.apt
+++ b/content/apt/developers/release/maven-project-release-procedure.apt
@@ -57,12 +57,12 @@ Performing a Maven Project Release
[]
-* Consider updating the parent versions
+** Consider updating the parent versions
If the item you are planning to release is not using the most recent version
of its parent
(see {{{../../pom/}parent POMs}} index), consider taking this opportunity to
update to it.
-* Consider updating the project dependencies
+** Consider updating the project dependencies
Generally it is a good that project use tha latest available versions of
used dependencies.
@@ -78,7 +78,7 @@ Performing a Maven Project Release
[]
-** Check release note at GitHub
+** Check release notes at GitHub
If a component has a history of release notes at <<GitHub>>, we should to
continue maintain it in order to avoid user confusing.
@@ -181,20 +181,14 @@ https://github.com/apache/<repository-name>/issues
-----
- The "vote is open for at least 72 hours" means that you need to wait <at
least> 72 hours before proceeding.
- This gives others time to test your release and check that everything is
good. If after that period you have not received
- enough +1 votes to reach the quorum, this doesn't mean the vote failed: it
just takes a bit longer.
- Checking binary output, ideally to control that the build is reproducible,
can be done by running <<<verify>>> (NOT <<<install>>>)
- followed by <<<artifact:compare>>> against the staged content:
------
-mvn -Papache-release -Dgpg.skip clean verify \
- artifact:compare
-Dreference.repo=https://repository.apache.org/content/repositories/staging/
------
+* Check the vote results
+ The "vote is open for at least 72 hours" means that you need to wait <at
least> 72 hours before proceeding.
+ This gives others time to test your staged release and check that everything
is good, with the help of our
{{{/guides/development/guide-testing-releases.html}Guide to testing staged
releases}}.
-* Check the vote results
+ If after that period you have not received enough +1 votes to reach the
quorum, this doesn't mean the vote failed: it just takes a bit longer.
Copied from
{{{https://www.apache.org/foundation/voting.html#ReleaseVotes}Votes on Package
Releases}}.
diff --git a/content/apt/guides/development/guide-testing-releases.apt
b/content/apt/guides/development/guide-testing-releases.apt
index c1a980c0..a1d2c55b 100644
--- a/content/apt/guides/development/guide-testing-releases.apt
+++ b/content/apt/guides/development/guide-testing-releases.apt
@@ -28,7 +28,7 @@
Guide to Testing Staged Releases
- As part of the release process, the artifacts are staged in a temporary
repository
+ As part of {{{/developers/release/index.html}the release process}}, the
artifacts are staged in a temporary repository
for testing and evaluation before voting. Such repositories are not
available by
default, so to use them your project must be configured appropriately.
@@ -71,6 +71,13 @@ mvn -Papache-release -Dgpg.skip clean verify \
artifact:compare
-Dreference.repo=https://repository.apache.org/content/groups/staging/
-----
+ Results of this check should be shared when voting, see for example:
+
+ * successful check results:
{{{https://lists.apache.org/thread/oodn7t2dmqdb0s9vr8dc0ocr71dqfsbl}one
approach}} or
{{{https://lists.apache.org/thread/5swm1phkpbmvt9bt6vb3r0qroczf90o1}another}}.
+
+ * un-successful check results: can be either found
{{{https://lists.apache.org/thread/ksdgkfr7x3wgld3ys5z75nfmp328p6k2}serious
enough to vote -1}},
+ or {{{https://lists.apache.org/thread/d2hh4d8kzrxs04mdl6v3py1v8hdtfyqt}not
blocking}}
({{{https://lists.apache.org/thread/8hlwosrxdptttjl363q0j86wp9yr27fo}another}})
based on impact of unexpected content in staged release.
+
* Setting up Archiva to Test Staged Releases
These steps will be similar for any repository manager - please refer to
their individual documentation for instructions on how to
