Re: [ee4j-pmc] git tags naming convention?

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

Ok, so the consensus seems to be to use annotated tags.

Here's a related question...

In an ideal world, a final release of a project will be staged, the
release review will be successful, and the staged artifacts will be
released.

But what happens if a problem is discovered after staging and before
release, or if the release review fails?  What if the project *needs*
to be updated before it is re-staged and released?

In such a scenario, when should the git tag for the release be applied?
My understanding is that changing the commit that a git tag refers to is
problematic after the repository has been shared with others.

Is it better to apply and push the git tag for the release when the
artifacts are staged, and accept the risk that in the unlikely scenario
the tag may need to be changed?

Or is it better to wait until the release is approved and apply the git
tag for the release after the fact?

I'm assuming most everyone is doing the former, but I wanted to ask just
to make sure that's actually considered the "best practice".

Thanks.


Bill Shannon wrote on 10/01/2018 03:55 PM:
> Is there an EE4J-wide convention for how to name the git tags for
> releases of various sorts?
> _______________________________________________
> ee4j-pmc mailing list
> ee4j-pmc@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
>