Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1

2018-06-12 Thread Remko Popma
+1 (Shameless plug) Every java main() method deserves http://picocli.info > On Jun 13, 2018, at 9:03, Gary Gregory wrote: > > I started reading the site, which is good so far... should be able to > continue tomorrow... > > Gary > >> On Tue, Jun 12, 2018, 17:35 Ralph Goers wrote: >> >> 48 ho

Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1

2018-06-12 Thread Gary Gregory
I started reading the site, which is good so far... should be able to continue tomorrow... Gary On Tue, Jun 12, 2018, 17:35 Ralph Goers wrote: > 48 hours have passed with no votes or discussion. > > Ralph > > > On Jun 10, 2018, at 2:26 PM, Ralph Goers > wrote: > > > > This is a vote to release

Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1

2018-06-12 Thread Ralph Goers
48 hours have passed with no votes or discussion. Ralph > On Jun 10, 2018, at 2:26 PM, Ralph Goers wrote: > > This is a vote to release Log4j-Audit 1.0.0, the first release of the Log4j > Audit project. > > Please download, test, and cast your votes on the log4j developers list. > [] +1, rele

Re: [log4net] crafting the next release

2018-06-12 Thread Dominik Psenner
That's an interesting question to ask. As I see it, ci should produce good and final artifacts. This means that ci should also sign them in the pipeline. We can inject required keys and credentials with secret variables to make it work. These credentials are then only accessible to whoever has acce

Re: [Java] TravisCI issue

2018-06-12 Thread Matt Sicker
I think it does. That's the plan, anyways. Not sure when the great Java 8 migration will begin, though. On 12 June 2018 at 12:35, Ralph Goers wrote: > Doesn’t master require Java 8 anyway? > > Ralph > > > On Jun 12, 2018, at 10:11 AM, Matt Sicker wrote: > > > > They don't appear to have Java 7

Re: [Java] TravisCI issue

2018-06-12 Thread Ralph Goers
Doesn’t master require Java 8 anyway? Ralph > On Jun 12, 2018, at 10:11 AM, Matt Sicker wrote: > > They don't appear to have Java 7 installed anymore or at least not > available in the usual location. A hybrid Java 8/10 build setup would be > good enough IMO. > > -- > Matt Sicker

Re: [log4j] 2.11.1 release timeline

2018-06-12 Thread Ralph Goers
Most of the release can be done by anybody but a few steps require that you be a PMC member. I’m still busy at work but not completely underwater. I need to take a look at some of the outstanding issues I would like to have fixed and see if I can knock some out quickly. I also promised to look

[Java] TravisCI issue

2018-06-12 Thread Matt Sicker
They don't appear to have Java 7 installed anymore or at least not available in the usual location. A hybrid Java 8/10 build setup would be good enough IMO. -- Matt Sicker

Re: [log4net] crafting the next release

2018-06-12 Thread Matt Sicker
Will you be signing and uploading them locally or via Jenkins? On Tue, Jun 12, 2018 at 10:05, Dominik Psenner wrote: > Hi, > > our CI is ready to supply us with binaries along with the log4net > website. This will be the first time that binaries from the CI are > shipped as a release. Therefore

Re: [log4j] 2.11.1 release timeline

2018-06-12 Thread Gary Gregory
The earlier the better ;-) We need an RM to volunteer, that's been Ralph in the past mostly. Gary On Tue, Jun 12, 2018 at 9:26 AM Carter Kozak wrote: > Hi all, > > Do we have a release schedule for 2.11.1? I'm more than happy to > assist with the process. > > Best, > -ck >

[log4j] 2.11.1 release timeline

2018-06-12 Thread Carter Kozak
Hi all, Do we have a release schedule for 2.11.1? I'm more than happy to assist with the process. Best, -ck

[log4net] crafting the next release

2018-06-12 Thread Dominik Psenner
Hi, our CI is ready to supply us with binaries along with the log4net website. This will be the first time that binaries from the CI are shipped as a release. Therefore we seek out for volunteers who evaluate the CI binaries [1]. Doing so is a great help and allows us to take the next steps o