[maven-site] branch master updated: reorder steps according to current reality

[hb...@apache.org]

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 4f0d252  reorder steps according to current reality
4f0d252 is described below

commit 4f0d252a33ca3db499c32ba1c8f320345691d845
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Sun Apr 4 18:46:49 2021 +0200

    reorder steps according to current reality
---
 .../developers/release/maven-core-release.md       | 30 ++++++++++++----------
 1 file changed, 16 insertions(+), 14 deletions(-)

diff --git a/content/markdown/developers/release/maven-core-release.md b/content/markdown/developers/release/maven-core-release.md
index b663007..f94f7e2 100644
--- a/content/markdown/developers/release/maven-core-release.md
+++ b/content/markdown/developers/release/maven-core-release.md
@@ -75,27 +75,15 @@ To produce a final release, the same process as for standard projects is followe
 
 Below describes the additional steps that need to be taken at the points where the website are updated in those instructions.
 
-#### Update the DOAP Information
-
-Edit <https://github.com/apache/maven/blob/master/doap_Maven.rdf> to list the new release.
-
-#### Update the Release Notes and Web Site
+#### Prepare the Release Notes
 
 Checkout Maven site source <https://github.com/apache/maven-site.git>.
 
-Note that release notes can be created and checked in, but other changes should not be checked in as it can be deployed 'live' at any time.
-
-- For 3.x: update the `versions3x`, `currentStableVersion` and `currentStableReleaseDate` properties in `pom.xml`
-
-Next, create the release notes:
+Create the release notes:
 
 - create `content/markdown/docs/$version`
 - create `content/markdowndocs/$version/release-notes.md` (see other versions for an example)
 
-Next, update release history `content/markdown/docs/history.md.vm`.
-
-Only deploy the site once the release is present on the mirrors, and the reference documentation has been deployed to [/ref/](/ref).
-
 #### Stage the Latest Documentation
 
 Once the release is prepared, but before the release vote, the site needs to be staged.
@@ -122,6 +110,20 @@ moved to the release svnpubsub tree:
 svn mv https://dist.apache.org/repos/dist/dev/maven/maven-3/$VERSION https://dist.apache.org/repos/dist/release/maven/maven-3 -m "Publish Maven Distribution Archives"
 ```
 
+#### Update the DOAP Information
+
+Edit <https://github.com/apache/maven/blob/master/doap_Maven.rdf> to list the new release.
+
+#### Update the Web Site
+
+Checkout Maven site source <https://github.com/apache/maven-site.git>.
+
+For 3.x: update the `versions3x`, `currentStableVersion` and `currentStableReleaseDate` properties in `pom.xml`
+
+Next, update release history `content/markdown/docs/history.md.vm`.
+
+Only deploy the site once the release is present on the mirrors, and the reference documentation has been deployed to [/ref/](/ref).
+
 #### Deploy the Latest Documentation to Target Versioned Location
 
 The reference documentation for Maven core source code references and API docs has been staged in a previous step: now it needs to be deployed to its dedicated directory before deploying the web site pointing to the new version.