You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by hb...@apache.org on 2020/05/31 09:56:15 UTC
[maven-site] branch master updated: avoid unwanted syntax color and
line numbering
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 e9c6300 avoid unwanted syntax color and line numbering
e9c6300 is described below
commit e9c63007a93faf39e419eed69b0ea154a334fae0
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Sun May 31 11:56:07 2020 +0200
avoid unwanted syntax color and line numbering
---
.../release/maven-project-release-procedure.apt | 28 +++++++++++-----------
1 file changed, 14 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 16f5c07..1f55207 100644
--- a/content/apt/developers/release/maven-project-release-procedure.apt
+++ b/content/apt/developers/release/maven-project-release-procedure.apt
@@ -81,7 +81,7 @@ Performing a Maven Project Release
Propose a vote on the dev list with the closed issues, the issues left,
the staging repository and the staging site. For instance:
-+-----+
+-----
To: "Maven Developers List" <de...@maven.apache.org>
Subject: [VOTE] Release Apache Maven XXX Plugin version Y.Z
@@ -112,7 +112,7 @@ Vote open for at least 72 hours.
[ ] +0
[ ] -1
-+-----+
+-----
To get the JIRA release notes link, browse to the plugin's JIRA page, select the <Road Map> link,
and use the link to <Release Notes> that is next to the version being released.
@@ -128,7 +128,7 @@ Vote open for at least 72 hours.
Copied from {{{https://www.apache.org/foundation/voting.html#ReleaseVotes}Votes on Package Releases}}.
-+-----+
+-----
Votes on whether a package is ready to be released use majority approval
-- i.e. at least three PMC members must vote affirmatively for release,
and there must be more positive than negative votes. Releases may not be vetoed.
@@ -136,13 +136,13 @@ Generally the community will cancel the release vote if anyone identifies seriou
but in most cases the ultimate decision, lies with the individual serving as release manager.
The specifics of the process may vary from project to project,
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:
-+-----+
+-----
To: "Maven Developers List" <de...@maven.apache.org>
CC: "Maven Project Management Committee List" <pr...@maven.apache.org>
Subject: [RESULT] [VOTE] Release Apache Maven XXX Plugin version Y.Z
@@ -156,7 +156,7 @@ The vote has passed with the following result:
PMC quorum: ...
I will promote the artifacts to the central repo.
-+-----+
+-----
If the vote is unsuccessful, 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}Dropping a Repo}}.
@@ -177,11 +177,11 @@ I will promote the artifacts to the central repo.
For example:
-+--------+
+--------
wagon/wagon-2.2-source-release.zip
wagon/wagon-2.2-source-release.zip.asc
wagon/wagon-2.2-source-release.zip.sha512
-+--------+
+--------
You should also run 'svn rm' as needed to clear out older releases. As per {{{https://www.apache.org/dev/release.html#where-do-releases-go}the release policy}},
only the latest release on a branch should stay in the main dist areas. So long as the previous release is at least a day old, the automatic archiver
@@ -240,10 +240,10 @@ wagon/wagon-2.2-source-release.zip.sha512
<<send>>, the announcement for you. First make sure that you have configured the necessary
properties in your {{{../committer-settings.html}committer settings}}.
-+------+
+------
cd target/checkout
mvn changes:announcement-mail -Papache-release
-+------+
+------
If sending the mail should fail, the generated annoucement is available in <<<target/annoucement>>> (see <<<annoucement.vm>>>)
and you can use it as a base for sending the mail manually.
@@ -251,17 +251,17 @@ mvn changes:announcement-mail -Papache-release
If your SMTP server requires authentication you need to add the command line
options for it:
-+------+
+------
cd target/checkout
mvn changes:announcement-mail -Dchanges.username=<SMTP-USERNAME> -Dchanges.password=<SMTP-PASSWORD> -Papache-release
-+------+
+------
[[b]] Manually
<<Note:>> You must send this email from your apache email account, e.g. YOUR_APACHE_USERNAME@apache.org otherwise
the email to announce@maven.apache.org will bounce.
-+-----+
+-----
From: YOUR_APACHE_USERNAME@apache.org
To: announce@maven.apache.org, users@maven.apache.org
Cc: dev@maven.apache.org
@@ -293,7 +293,7 @@ Enjoy,
-The Apache Maven team
-+-----+
+-----
[]