[
https://issues.apache.org/jira/browse/VELOCITY-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18034851#comment-18034851
]
Claude Brisson commented on VELOCITY-990:
-----------------------------------------
The script has a {--dry-run} option, here is an example output:
{code}
~/g/v/velocity-engine (master|✔) $ ./release.sh 2.4.2 RC1 --dry-run
Planned versions/tags:
RELEASE : 2.4.2
RC TAG : 2.4.2-RC1
FINAL TAG : 2.4.2
NEXT (default): 2.5-SNAPSHOT
Confirm the above. Press Enter to continue...
[DRY-RUN] git fetch --all --tags
[DRY-RUN] mvn -q -DskipTests -U verify
[DRY-RUN] mvn -Denforcer.skip=false -Drules=requireReleaseDeps enforcer:enforce
About to set project version to 2.4.2 and <scm><tag> to 2.4.2. Press Enter to
continue...
[DRY-RUN] mvn -q versions:set -DnewVersion=2.4.2
[DRY-RUN] mvn -q versions:commit
[DRY-RUN] mvn -q versions:set-scm-tag -DnewTag=2.4.2
[DRY-RUN] git add -A
[DRY-RUN] git commit -m Release 2.4.2: set versions to 2.4.2 and
<scm><tag>=2.4.2
About to create and push RC tag 2.4.2-RC1 at current commit. Press Enter to
continue...
[DRY-RUN] git tag -a 2.4.2-RC1 -m Velocity engine 2.4.2 (RC: RC1)
[DRY-RUN] git push origin refs/tags/2.4.2-RC1:refs/tags/2.4.2-RC1
About to run mvn release:perform from tag 2.4.2-RC1 (goals=deploy). Press Enter
to continue...
[DRY-RUN] mvn -B -e
-DconnectionUrl=scm:git:https://gitbox.apache.org/repos/asf/velocity-engine.git
-Dtag=2.4.2-RC1 -Dgoals=deploy -Darguments=-Dgpg.sign=true -DskipTests
-Papache-release release:perform
[DRY-RUN] mkdir -p target/velocity-staging/engine/2.4.2
====================================================================
Dist/dev staging assembled in:
target/velocity-staging/engine/2.4.2
Now copy the contents of that directory to your local checkout of:
https://dist.apache.org/repos/dist/dev/velocity/engine/2.4.2/
Then: svn add/commit there.
====================================================================
Vote email skeleton generated at: target/engine-2.4.2-rc-vote.txt
Enter NEXT development version [default: 2.5-SNAPSHOT]:
About to bump to 2.5-SNAPSHOT and reset <scm><tag>=HEAD. Press Enter to
continue...
[DRY-RUN] mvn -q versions:set -DnewVersion=2.5-SNAPSHOT
[DRY-RUN] mvn -q versions:commit
[DRY-RUN] mvn -q versions:set-scm-tag -DnewTag=HEAD
[DRY-RUN] git add -A
[DRY-RUN] git commit -m Start 2.5-SNAPSHOT (reset <scm><tag>=HEAD)
[DRY-RUN] git push origin master
Done.
{code}
> Releasing: make sure that scm/tag in pom.xml matches git tag
> ------------------------------------------------------------
>
> Key: VELOCITY-990
> URL: https://issues.apache.org/jira/browse/VELOCITY-990
> Project: Velocity
> Issue Type: Task
> Reporter: Peter Palaga
> Priority: Major
> Attachments: release.sh
>
>
> Hi, I noticed the following issue on recent releases that were preceded by
> RCs:
> The scm/tag is the RC version, not the actually released version that is
> present in <version> and that would match git tag.
> For example, for release 2.4.1, the tag and versions in pom.xml files are all
> {{2.4.1}}, but the scm/tag is
> {code:xml}
> <scm>
> ...
> <tag>2.4.1-rc1</tag>
> </scm>
> {code}
> Could you please adjust your processes next time, to make rebuilds easier?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
