This is an automated email from the ASF dual-hosted git repository.
robertlazarski pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-core.git
The following commit(s) were added to refs/heads/master by this push:
new a03ab08 update release-process docs for git
a03ab08 is described below
commit a03ab081a3daf1e3250ac2c2d07efadcdde75374
Author: Robert Lazarski <[email protected]>
AuthorDate: Sun Aug 1 05:31:36 2021 -1000
update release-process docs for git
---
src/site/markdown/release-process.md | 18 +++++-------------
1 file changed, 5 insertions(+), 13 deletions(-)
diff --git a/src/site/markdown/release-process.md
b/src/site/markdown/release-process.md
index 42d4ace..82f5554 100644
--- a/src/site/markdown/release-process.md
+++ b/src/site/markdown/release-process.md
@@ -161,11 +161,6 @@ In order to prepare the release artifacts for vote,
execute the following steps:
mvn release:prepare
When asked for a tag name, accept the default value (in the following
format: `vX.Y.Z`).
- The execution of the `release:prepare` goal may occasionally fail because
`svn.apache.org`
- resolves to one of the geolocated SVN mirrors and there is a propagation
delay between
- the master and these mirrors. If this happens,
- wait for a minute (so that the mirrors can catch up with the master) and
simply rerun the command.
- It will continue where the error occurred.
2. Perform the release using the following command:
@@ -178,20 +173,17 @@ In order to prepare the release artifacts for vote,
execute the following steps:
5. Create a staging area for the Maven site:
- svn cp https://svn.apache.org/repos/asf/axis/site/axis2/java/core \
-
https://svn.apache.org/repos/asf/axis/site/axis2/java/core-staging
+ git clone https://gitbox.apache.org/repos/asf/axis-site.git
+ cp -r axis2/java/core/ axis2/java/core-staging
+ git add axis2/java/core-staging
+ git commit -am "create core-staging"
+ git push
6. Change to the `target/checkout` directory and prepare the site using the
following commands:
mvn site-deploy
mvn scm-publish:publish-scm -Dscmpublish.skipCheckin=true
- Now go to the `target/scmpublish-checkout` directory (relative to
`target/checkout`) and check that there
- are no unexpected changes to the site. Then commit the changes.
- Note that this may fail because of
[INFRA-11007](https://issues.apache.org/jira/browse/INFRA-11007).
- In this case, switch to the Subversion master using the following command
before trying to commit again:
-
- svn switch --relocate https://svn.apache.org/
https://svn-master.apache.org/
7. Start the release vote by sending a mail to `[email protected]`.
The mail should mention the following things:
