[incubator-baremaps] branch 492-release-wip updated (54696abc -> cf5612a5)

[bc...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

bchapuis pushed a change to branch 492-release-wip
in repository https://gitbox.apache.org/repos/asf/incubator-baremaps.git


 discard 54696abc Add release instructions
     new cf5612a5 Add release instructions

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (54696abc)
            \
             N -- N -- N   refs/heads/492-release-wip (cf5612a5)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

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.


Summary of changes:
 RELEASE.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

[incubator-baremaps] 01/01: Add release instructions

[bc...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

bchapuis pushed a commit to branch 492-release-wip
in repository https://gitbox.apache.org/repos/asf/incubator-baremaps.git

commit cf5612a5148f6697ca04f368464cd4da5ca9668d
Author: Bertil Chapuis <bc...@gmail.com>
AuthorDate: Tue Mar 7 13:57:54 2023 +0100

    Add release instructions
---
 RELEASE.md | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/RELEASE.md b/RELEASE.md
new file mode 100644
index 00000000..f0c5cc1d
--- /dev/null
+++ b/RELEASE.md
@@ -0,0 +1,19 @@
+# Release instructions
+
+In order to release a new version of baremaps, follow these steps:
+
+1. Notify the community of the upcoming release by creating a new issue on GitHub.
+2. Notify the community by sending a message on the mailing list and ask to pause commits on the main branch.
+3. Create a new branch for the release.
+4. Create a release candidate by running the following command:
+
+```bash 
+mvn release:prepare -DautoVersionSubmodules=true -DgenerateBackupPoms=false
+```
+
+5. Set the release version (e.g. 1.0.0).
+6. Set the tag name (e.g. v1.0.0-rc1).
+7. Set the next development version (e.g. 1.0.1-SNAPSHOT).
+8. Ask the community to test the release candidate.
+9. If the release candidate is not approved by the community, perform the necessary changes and go back to step 4.
+10. If the release candidate is approved by the community, rename the tag (e.g. v1.0.0), push the changes to the main branch, generate the release notes on GitHub, and notify the community.