This is an automated email from the ASF dual-hosted git repository.
desruisseaux pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/sis-site.git
commit 4fef9a52b2f30791fa96a981a63aae80c320af71
Author: Martin Desruisseaux <martin.desruisse...@geomatys.com>
AuthorDate: Sat Sep 30 17:20:16 2023 +0200
Remove duplicated section.
---
content/release-management.md | 34 ++++++----------------------------
1 file changed, 6 insertions(+), 28 deletions(-)
diff --git a/content/release-management.md b/content/release-management.md
index 1e770233..48935bf0 100644
--- a/content/release-management.md
+++ b/content/release-management.md
@@ -30,18 +30,22 @@ Before to perform a release, make sure that the following
conditions hold:
## Directory layout {#directory-layout}
-The steps described in this page assume the following directory layout.
+The steps described in this page assume the following directory layout,
+where `$NEW_VERSION` and `$RELEASE_CANDIDATE` are environment variables
introduced [later](#configure).
Some directories are Git checkout, other are ordinary directories. Any other
layout can be used,
provided that all relative paths in this page are adjusted accordingly.
{{< highlight text >}}
<any root directory for SIS>
+├─ $NEW_VERSION-RC
├─ main
├─ non-free
│ ├─ sis-epsg
│ └─ sis-embedded-data
├─ release
│ ├─ distribution
+│ │ └─ $NEW_VERSION
+│ │ └─ RC$RELEASE_CANDIDATE
│ └─ test
│ ├─ integration
│ └─ maven
@@ -166,7 +170,7 @@ the current release attempt. Those versions shall be set on
the command line lik
{{< highlight bash >}}
gpg --list-keys # For getting the value to put in <your
key ID>
unset PATH_TO_FX
-export OLD_VERSION=1.2
+export OLD_VERSION=1.3
export NEW_VERSION={{% version %}}
export RELEASE_CANDIDATE=1
export SIGNING_KEY=<your key ID> # hexadecimal number with 8 or 40 digits.
@@ -175,32 +179,6 @@ export SIGNING_KEY=<your key ID> # hexadecimal number
with 8 or 40 digits.
Make sure that the code signing key is the defauly key declared in
`~/.gnupg/gpg.conf`
during the Maven deployment phase.
-## Directory layout {#directory-layout}
-
-The steps described in this page assume the following directory layout (some
directories will be created as
-a result of the steps). Any other layout can be used. However if the layout
differs, then the relative paths
-in this page shall be adjusted accordingly.
-
-{{< highlight text >}}
- <any root directory for SIS>
- ├─ $NEW_VERSION-RC
- ├─ master
- ├─ non-free
- │ └─ sis-epsg
- ├─ releases
- │ ├─ distribution
- │ │ └─ $NEW_VERSION
- │ │ └─ RC$RELEASE_CANDIDATE
- │ └─ tests
- │ ├─ integration
- │ └─ maven
- └─ site
- ├─ main
- ├─ asf-staging
- ├─ asf-site
- └─ javadoc
-{{< / highlight >}}
-
# Review project status before branching {#prepare-source}
Replace the `$OLD_VERSION` number by `$NEW_VERSION` in the values of following
properties on the development branch:
