I've updated the git tag to be v12.0-rc2 and am deleting the v12.0 tag. The v12.0 tag will be created upon a successful release vote.
On Sun, 9 Feb 2020 at 13:01, Ralph Goers <[email protected]> wrote: > > 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 <[email protected]> wrote: > > > > I see that log4j2 artifacts use the rcN suffix in the <tag> 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 <[email protected]> wrote: > >> > >> 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 <[email protected]> wrote: > >>> > >>> 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 > >>> understanding erroneous? > >>> > >>> Gary > >>> > >>> On Sat, Feb 8, 2020 at 3:01 PM Matt Sicker <[email protected]> wrote: > >>> > >>>> Hello all, this is a vote to release the second release candidate of > >>>> Log4j Scala API 12.0. This vote will remain open for at least 72 hours > >>>> and requires at least 3 +1 votes and more +1 votes than -1 votes. > >>>> > >>>> == Links > >>>> > >>>> Staging repository: > >>>> https://repository.apache.org/content/repositories/orgapachelogging-1052 > >>>> > >>>> Staging artifacts: > >>>> https://dist.apache.org/repos/dist/dev/logging/log4j/scala/ > >>>> > >>>> Site preview: > >>>> https://jvz.github.io/log4j-scala-site/ > >>>> > >>>> Repository: > >>>> https://gitbox.apache.org/repos/asf?p=logging-log4j-scala.git > >>>> > >>>> Tag: > >>>> v12.0 > >>>> > >>>> You may download all the Maven artifacts by executing: > >>>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate > >>>> https://repository.apache.org/content/repositories/orgapachelogging-1052 > >>>> > >>>> == ChangeLog > >>>> > >>>> New Features:: > >>>> LOG4J2-1882::: Migrate log4j-api-scala to sbt. > >>>> LOG4J2-2303::: Add release distribution script. > >>>> LOG4J2-2295::: Add OSGi metadata to release jars. > >>>> LOG4J2-2294::: Add release audit information to build. > >>>> LOG4J2-2298::: Add changelog to site. > >>>> LOG4J2-2293::: Add required license files to sbt output artifacts. > >>>> LOG4J2-2296::: Add sbt-site plugin and website configuration. > >>>> LOG4J2-2291::: Add Jenkins pipeline for sbt build. > >>>> LOG4J2-2668::: Add support for Scala 2.13. > >>>> > >>>> Changes:: > >>>> LOG4J2-2309::: Update Log4j Scala API for 2.13 from 2.13.0-M2 to > >>>> 2.13.0-M3. > >>>> LOG4J2-2290::: Update Log4j from 2.9.1 to 2.11.0. > >>>> LOG4J2-1995::: Update log4j-api-scala_2.11 from Scala 2.11.8 to 2.11.11. > >>>> LOG4J2-1996::: Update log4j-api-scala_2.12 from Scala 2.12.1 to 2.12.3. > >>>> LOG4J2-2115::: Update Log4j dependency from 2.8.1 to 2.9.1. > >>>> LOG4J2-2116::: Update log4j-api-scala_2.12 from Scala 2.12.3 to 2.12.4. > >>>> > >>>> > >>>> -- > >>>> Matt Sicker <[email protected]> > >>>> > >> > >> -- > >> Matt Sicker <[email protected]> > > > > > > > > -- > > Matt Sicker <[email protected]> > > > > -- Matt Sicker <[email protected]>
