> If there is a recommendation for tag
names, perhaps the following article
> could be updated to reflect it:
> https://wiki.eclipse.org/JakartaEE_New_Infra_Release_Job
> As it still adds the -RELEASE suffix and
is not using annotation on the tag.
Yes, we should fix that. Or you can! It's a
wiki! :-)
I have just had a go at doing it but didn't
complete it because there is a problem. I
could change it to manipulate the script quite
easily, it would be just to change:
RELEASE_TAG="${RELEASE_VERSION}-RELEASE"
git push --delete origin "${RELEASE_TAG}"
&& true (to git push --delete origin
refs/tags/"${RELEASE_TAG}" && true)
But then we need to decide what to do with
the branching:
git checkout -b ${RELEASE_VERSION}
Would create a branch with the same name
due to:
RELEASE_VERSION=`echo ${SNAPSHOT_VERSION} |
sed -e 's/-SNAPSHOT//'`
Which is also pushed to GitHub:
git push origin "${RELEASE_VERSION}"
On it's own that is not too bad, it's just
that with GitHub when you have a branch and a
tag with the same name it defaults to viewing
the branch in the UI and I can't seem to find
a way to force it to view the tag.
