You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by sj...@apache.org on 2022/11/02 18:16:39 UTC
[maven-site] branch MNGSITE-498 created (now f4472df2)
This is an automated email from the ASF dual-hosted git repository.
sjaranowski pushed a change to branch MNGSITE-498
in repository https://gitbox.apache.org/repos/asf/maven-site.git
at f4472df2 [MNGSITE-498] Clarify procedure for restarting releases
This branch includes the following new commits:
new f4472df2 [MNGSITE-498] Clarify procedure for restarting releases
The 1 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.
[maven-site] 01/01: [MNGSITE-498] Clarify procedure for restarting releases
Posted by sj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
sjaranowski pushed a commit to branch MNGSITE-498
in repository https://gitbox.apache.org/repos/asf/maven-site.git
commit f4472df2931697fcf4cca37e0e0a18ae980d628e
Author: Slawomir Jaranowski <s....@gmail.com>
AuthorDate: Wed Nov 2 19:15:07 2022 +0100
[MNGSITE-498] Clarify procedure for restarting releases
---
.../release/maven-project-release-procedure.apt | 37 +++++++++++++++++++---
1 file changed, 33 insertions(+), 4 deletions(-)
diff --git a/content/apt/developers/release/maven-project-release-procedure.apt b/content/apt/developers/release/maven-project-release-procedure.apt
index 8ec8d5e7..a22b50f6 100644
--- a/content/apt/developers/release/maven-project-release-procedure.apt
+++ b/content/apt/developers/release/maven-project-release-procedure.apt
@@ -140,7 +140,9 @@ but the 'minimum quorum of three +1 votes' rule is universal.
The list of PMC members is available at {{https://people.apache.org/committers-by-project.html#maven-pmc}}.
- Once a vote is successful, post the result to the dev list and cc the PMC. For instance:
+** Successful vote
+
+ Once a vote is <<successful>>, post the result to the <<<dev>>> list and cc the <<<PMC>>>. For instance:
-----
To: "Maven Developers List" <de...@maven.apache.org>
@@ -158,14 +160,41 @@ PMC quorum: ...
I will promote the source release zip file to Apache distribution area and the artifacts to the central repo.
-----
- If the vote is <<unsuccessful>>, the process will need to be restarted. Be sure to:
+ Follow the procedure to the end.
+
+** Unsuccessful vote
+
+ Once a vote is <<unsuccessful>>, post the result to the <<<dev>>> list, For instance:
- * drop your staging repository as described in {{{https://www.apache.org/dev/publishing-maven-artifacts.html#drop}Dropping a Repo}}.
+-----
+To: "Maven Developers List" <de...@maven.apache.org>
+Subject: [CANCEL] [VOTE] Release Apache Maven XXX Plugin version Y.Z
+
+Hi,
+
+The vote has been canceled.
+-----
- * remove the release from the corresponding github release {{{https://github.com/apache/maven/releases}https://github.com/apache/<maven-project>/releases}}
+ For canceled vote the process will need to be restarted.
+
+ Be sure to:
+
+ * drop your staging repository as described in {{{https://www.apache.org/dev/publishing-maven-artifacts.html}Drop a repository}}
+
+ * create new version for next round <<<Y.Z+1>>>
+
+ * assign issues from version <<<Y.Z>>> also to version <<<Y.Z+1>>>
+
+ * mark the <<<Y.Z>>> version as <<archived>>
+
+ * report found issues and assign them to version <<<Y.Z+1>>>
+
+ * fix found issues
[]
+ Start the process for version <<<Y.Z+1>>> from the beginning.
+
* Copy the source release to the Apache Distribution Area
The official Apache release is the 'source-release' bundle distributed in <<<www.apache.org/dist>>>,