Hi Matt:

We need to SHA1 files in
https://dist.apache.org/repos/dist/dev/logging/log4j/scala/

Gary

On Mon, Apr 9, 2018 at 1:32 PM, Matt Sicker <boa...@gmail.com> wrote:

> Hello all, this is a vote to release 11.1 rc1 of Log4j Scala API. This
> release is the first release being done using sbt instead of maven. This is
> also the first release that supports Scala 2.13.0-M3 for early testers.
>
> This vote will remain open for at least 72 hours and requires at least 3
> +1s and more +1s than -1s.
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachelogging-1034/
>
> Staging artifacts:
> https://dist.apache.org/repos/dist/dev/logging/log4j/scala/
>
> Site preview:
> https://jvz.github.io/log4j-scala-site/
>
> Git repo:
> https://git-wip-us.apache.org/repos/asf/logging-log4j-scala.git
>
> Tag:
> v11.1-rc1
>
> 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-1034/org/apache/logging/log4j/
>
> 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.
> Bug Fixes
>
> None.
> 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.
> Removed
>
> None.
>
>
> --
> Matt Sicker <boa...@gmail.com>
>

Reply via email to