The vote passes with 3 +1 binding and 1 +1 unbinding votes.
I'll follow up with the release steps. Thankfully, the staging repo hasn't
disappeared like last time.
On Thu, 27 Dec 2018 at 10:17, Raman Gupta wrote:
> I guess I can +1 this now too.
>
> On Thu, Dec 27, 2018 at 11:11 AM Matt Sicker
I guess I can +1 this now too.
On Thu, Dec 27, 2018 at 11:11 AM Matt Sicker wrote:
>
> My +1 along with a +1 from Remko.
>
> On Sun, 2 Dec 2018 at 23:03, Ralph Goers wrote:
>
> > Sorry for taking so long. I somehow missed this thread. Hopefully others
> > will also review it.
> >
> > +1
> >
> >
My +1 along with a +1 from Remko.
On Sun, 2 Dec 2018 at 23:03, Ralph Goers wrote:
> Sorry for taking so long. I somehow missed this thread. Hopefully others
> will also review it.
>
> +1
>
> Ralph
>
> > On Nov 3, 2018, at 1:16 PM, Matt Sicker wrote:
> >
> > GPG keys:
> > https://dist.apache.org
Sorry for taking so long. I somehow missed this thread. Hopefully others will
also review it.
+1
Ralph
> On Nov 3, 2018, at 1:16 PM, Matt Sicker wrote:
>
> GPG keys:
> https://dist.apache.org/repos/dist/release/logging/KEYS
>
> Signed by Matt Sicker (748F15B2CF9BA8F024155E6ED7C92B70FA1C814D)
I've also put together an updated release guide based on the Log4j 2 one:
https://cwiki.apache.org/confluence/display/LOGGING/Log4j+Kotlin+API+Release+Process
On Sat, 3 Nov 2018 at 15:16, Matt Sicker wrote:
> GPG keys:
> https://dist.apache.org/repos/dist/release/logging/KEYS
>
> Signed by Matt
GPG keys:
https://dist.apache.org/repos/dist/release/logging/KEYS
Signed by Matt Sicker (748F15B2CF9BA8F024155E6ED7C92B70FA1C814D).
Site:
https://jvz.github.io/log4j-api-kotlin-staging/
Maven Central artifacts:
https://repository.apache.org/content/repositories/orgapachelogging-1040/
Git:
git c
