I like on both (the shortend tag names and the protected tags for releases )
Am 08.03.2025 um 09:11 schrieb Slawomir Jaranowski:
On Sat, 8 Mar 2025 at 09:03, Hervé Boutemy <hbout...@apache.org> wrote:
if we go from svn-oriented old conventions to benefit from more modern Git
ones, I'd like that we investigate Git tag best practices like RC tag during
votes and protected tag on final release
So it can be the next step to work with RC tag ... and protected tag
for it we will need update a release instruction and can be next discussion
but now we can change the tag name format as the first step.
Regards,
Hervé
Le samedi 8 mars 2025, 08:01:34 CET Slawomir Jaranowski a écrit :
Hi,
We use in Maven projects default tag name for release as:
{project.artifactId}-{project.version}
Such format will be ok for project releasing from one svn repository
... but now we use separate git for each project.
What do you think about changing it to something like: v{project.version}?
It will be a good time before the next parents release to change it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
