Yes, I use -rcn for the tag of the Log4j releases. After the release candidate
is released I then manually create a tag from the -rcn tag. Unfortunately, I
don’t always remember to do that.
Ralph
> On Feb 9, 2020, at 11:36 AM, Matt Sicker wrote:
>
> I see that log4j2 artifacts use the rcN suf
I see that log4j2 artifacts use the rcN suffix in the element of
the parent pom, so it seems that I may have tagged this in the wrong
order. I'll update the release process instructions.
On Sun, 9 Feb 2020 at 11:44, Matt Sicker wrote:
>
> I don’t think we’ve copied our tags over to rel yet. I wa
I don’t think we’ve copied our tags over to rel yet. I was able to force
push the tag. I’m not entirely certain how to go about tagging this as rc2
but making sure all the artifacts are unchanged if the vote passes.
On Sun, Feb 9, 2020 at 08:45 Gary Gregory wrote:
> The v12.0 tag can't be right.
The v12.0 tag can't be right. My understanding is that each RC MUST have
its own tag so we can track what we vote and have voted on, I had forgotten
that in RC1. Once a vote passes you can copy the tag to rel/whatever; since
"rel/" is a special place for Apache tags that is 'locked down'. Or. is my
