[glassfish-dev] Question about steps to release a new version of a glass

["sawamura.hiroki@xxxxxxxxxxx" <sawamura.hiroki@xxxxxxxxxxx>]

Hi,

I'm trying to release a new version of glassfish-security-plugin in relation to eclipse-ee4j/glassfish-security-plugin#9[*].
[*] https://github.com/eclipse-ee4j/glassfish-security-plugin/issues/9

This is my first time, so let me review the steps to create a release.

First, I researched how other projects are releasing, and I found the following Jenkins job:
https://ci.eclipse.org/glassfish/view/all/job/all-projects_1_build-and-stage/

My understanding is that if I set the appropriate parameters for this job and run it, the release process for the specified project will work automatically.
In this case,
 - PROJECT : glassfish-security-plugin
 - RELEASE_VERSION : 1.0.11
 - NEXT_VERSION : 1.0.12
 - BRANCH : master
 - DRY_RUN : false
 - OVERWRITE : false

I checked the pipeline configuration to be sure, the command of the version rewrite was as follows.
```
SNAPSHOT_VERSION=`mvn ${MVN_EXTRA} -B -C -U -Pstaging  ${HELP_PLUGIN}:evaluate \
				-Dexpression=project.version 2> /dev/null | \
                egrep '^[0-9]+\.[0-9]+(\.[0-9]+)?-SNAPSHOT$'`
(==snip==)
find . -name pom.xml -exec sed -i "s|<version>${SNAPSHOT_VERSION}</version>|<version>${RELEASE_VERSION}</version>|g" {} \;
```

For glassfish-security-plugin, 1.0.10 is already tagged, but the current project version is 1.0.10-SNAPSHOT.
So, the command that is actually executed is:
```
find . -name pom.xml -exec sed -i "s|<version>1.0.10-SNAPSHOT</version>|<version>1.0.11</version>|g" {} \;
```
Therefore, I'll probably need to manually change the project version to 1.0.11-SNAPSHOT step before jenkins job.

Has my understanding of that been correct so far?

- Hiroki