We are close for 2.1...

Discussion:

Gary Gregory

2014-10-06 17:03:03 UTC

Thanks to Matt's RM and coding efforts over the weekend, we went through
three RCs and found and resolved a slew of issues.

Thanks Matt once again.

It looks like Matt added the shutdown hook he had discussed and other OSGi
related changes. My Apache time is quite limited this week so if anyone
else can spend some time on reviewing and polishing 2.1, now is the time.

While the ML and Jira are active with new messages and tickets, it still
feels like pushing for 2.1 ASAP is the right thing to do, pending Matt's
availability.

Gary

--
E-Mail: ***@gmail.com | ***@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Ralph Goers

2014-10-06 17:49:05 UTC

Permalink

If Matt is not available I will have the time this week to do a release.

Ralph

Thanks to Matt's RM and coding efforts over the weekend, we went through three RCs and found and resolved a slew of issues.
Thanks Matt once again.
It looks like Matt added the shutdown hook he had discussed and other OSGi related changes. My Apache time is quite limited this week so if anyone else can spend some time on reviewing and polishing 2.1, now is the time.
While the ML and Jira are active with new messages and tickets, it still feels like pushing for 2.1 ASAP is the right thing to do, pending Matt's availability.
Gary
--
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition
Spring Batch in Action
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Matt Sicker

2014-10-06 18:02:45 UTC

Permalink

I should have time to start the release again (most likely tonight), but if
there's anything else we want to get in for 2.1, then I may have to step
down.

Post by Ralph Goers
If Matt is not available I will have the time this week to do a release.
Ralph
Thanks to Matt's RM and coding efforts over the weekend, we went through
three RCs and found and resolved a slew of issues.
Thanks Matt once again.
It looks like Matt added the shutdown hook he had discussed and other OSGi
related changes. My Apache time is quite limited this week so if anyone
else can spend some time on reviewing and polishing 2.1, now is the time.
While the ML and Jira are active with new messages and tickets, it still
feels like pushing for 2.1 ASAP is the right thing to do, pending Matt's
availability.
Gary
--
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

--
Matt Sicker <***@gmail.com>

Gary Gregory

2014-10-06 18:11:37 UTC

Permalink

I do not think we should add _anything_ for 2.1. If I have an itch before
2.1 I'll create a branch. Ideally, our time should be spent polishing.

Gary

Post by Matt Sicker
I should have time to start the release again (most likely tonight), but
if there's anything else we want to get in for 2.1, then I may have to step
down.

Post by Ralph Goers
If Matt is not available I will have the time this week to do a release.
Ralph
Thanks to Matt's RM and coding efforts over the weekend, we went through
three RCs and found and resolved a slew of issues.
Thanks Matt once again.
It looks like Matt added the shutdown hook he had discussed and other
OSGi related changes. My Apache time is quite limited this week so if
anyone else can spend some time on reviewing and polishing 2.1, now is the
time.
While the ML and Jira are active with new messages and tickets, it still
feels like pushing for 2.1 ASAP is the right thing to do, pending Matt's
availability.
Gary
--
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Matt Sicker

2014-10-06 19:19:40 UTC

Permalink

That's what I mean. Any more polishing? Any APIs you forgot to fix before
2.1 that can be done in a couple hours or so? That sort of thing.

Post by Gary Gregory
I do not think we should add _anything_ for 2.1. If I have an itch before
2.1 I'll create a branch. Ideally, our time should be spent polishing.
Gary

Post by Matt Sicker
I should have time to start the release again (most likely tonight), but
if there's anything else we want to get in for 2.1, then I may have to step
down.

Post by Ralph Goers
If Matt is not available I will have the time this week to do a release.
Ralph
Thanks to Matt's RM and coding efforts over the weekend, we went through
three RCs and found and resolved a slew of issues.
Thanks Matt once again.
It looks like Matt added the shutdown hook he had discussed and other
OSGi related changes. My Apache time is quite limited this week so if
anyone else can spend some time on reviewing and polishing 2.1, now is the
time.
While the ML and Jira are active with new messages and tickets, it still
feels like pushing for 2.1 ASAP is the right thing to do, pending Matt's
availability.
Gary
--
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

--
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

--
Matt Sicker <***@gmail.com>

Gary Gregory

2014-10-06 19:33:41 UTC

Permalink

Not here.

Gary

Post by Matt Sicker
That's what I mean. Any more polishing? Any APIs you forgot to fix before
2.1 that can be done in a couple hours or so? That sort of thing.

Post by Gary Gregory
I do not think we should add _anything_ for 2.1. If I have an itch before
2.1 I'll create a branch. Ideally, our time should be spent polishing.
Gary

Post by Matt Sicker
I should have time to start the release again (most likely tonight), but
if there's anything else we want to get in for 2.1, then I may have to step
down.

Post by Ralph Goers
If Matt is not available I will have the time this week to do a release.
Ralph
Thanks to Matt's RM and coding efforts over the weekend, we went
through three RCs and found and resolved a slew of issues.
Thanks Matt once again.
It looks like Matt added the shutdown hook he had discussed and other
OSGi related changes. My Apache time is quite limited this week so if
anyone else can spend some time on reviewing and polishing 2.1, now is the
time.
While the ML and Jira are active with new messages and tickets, it
still feels like pushing for 2.1 ASAP is the right thing to do, pending
Matt's availability.
Gary
--
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Remko Popma

2014-10-06 22:19:04 UTC

Permalink

I looked at the commit emails for the recent changes but nothing caught my eye; i'm fine with releasing what we have now.

FYI, I started a number of online courses and may have very little time to work on log4j for the next month or two.

Regards, -Remko

Sent from my iPhone

Post by Gary Gregory
Not here.
Gary

That's what I mean. Any more polishing? Any APIs you forgot to fix before 2.1 that can be done in a couple hours or so? That sort of thing.

I do not think we should add _anything_ for 2.1. If I have an itch before 2.1 I'll create a branch. Ideally, our time should be spent polishing.
Gary

I should have time to start the release again (most likely tonight), but if there's anything else we want to get in for 2.1, then I may have to step down.

Post by Ralph Goers
If Matt is not available I will have the time this week to do a release.
Ralph

Thanks to Matt's RM and coding efforts over the weekend, we went through three RCs and found and resolved a slew of issues.
Thanks Matt once again.
It looks like Matt added the shutdown hook he had discussed and other OSGi related changes. My Apache time is quite limited this week so if anyone else can spend some time on reviewing and polishing 2.1, now is the time.
While the ML and Jira are active with new messages and tickets, it still feels like pushing for 2.1 ASAP is the right thing to do, pending Matt's availability.
Gary
--
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition
Spring Batch in Action
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

--
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition
Spring Batch in Action
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Remko Popma

2014-10-12 00:47:36 UTC

Permalink

Just FYI, someone just asked for log4j-iostreams functionality on
Stackoverflow
<http://stackoverflow.com/questions/26318295/write-system-out-to-file-with-log4j2/26320693#26320693>.

I realize this is easy for me to say, but shall we release 2.1?

Post by Remko Popma
I looked at the commit emails for the recent changes but nothing caught my
eye; i'm fine with releasing what we have now.
FYI, I started a number of online courses and may have very little time to
work on log4j for the next month or two.
Regards, -Remko
Sent from my iPhone
Not here.
Gary

Post by Matt Sicker
That's what I mean. Any more polishing? Any APIs you forgot to fix before
2.1 that can be done in a couple hours or so? That sort of thing.

Post by Gary Gregory
I do not think we should add _anything_ for 2.1. If I have an itch
before 2.1 I'll create a branch. Ideally, our time should be spent
polishing.
Gary

Post by Matt Sicker
I should have time to start the release again (most likely tonight),
but if there's anything else we want to get in for 2.1, then I may have to
step down.

Post by Ralph Goers
If Matt is not available I will have the time this week to do a release.
Ralph
Thanks to Matt's RM and coding efforts over the weekend, we went
through three RCs and found and resolved a slew of issues.
Thanks Matt once again.
It looks like Matt added the shutdown hook he had discussed and other
OSGi related changes. My Apache time is quite limited this week so if
anyone else can spend some time on reviewing and polishing 2.1, now is the
time.
While the ML and Jira are active with new messages and tickets, it
still feels like pushing for 2.1 ASAP is the right thing to do, pending
Matt's availability.
Gary
--
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Ralph Goers

2014-10-12 03:43:57 UTC

Permalink

I thought Matt was going to do this. I am not sure what happened.

Ralph

Just FYI, someone just asked for log4j-iostreams functionality on Stackoverflow.
I realize this is easy for me to say, but shall we release 2.1?
I looked at the commit emails for the recent changes but nothing caught my eye; i'm fine with releasing what we have now.
FYI, I started a number of online courses and may have very little time to work on log4j for the next month or two.
Regards, -Remko
Sent from my iPhone

Post by Gary Gregory
Not here.
Gary
That's what I mean. Any more polishing? Any APIs you forgot to fix before 2.1 that can be done in a couple hours or so? That sort of thing.
I do not think we should add _anything_ for 2.1. If I have an itch before 2.1 I'll create a branch. Ideally, our time should be spent polishing.
Gary
I should have time to start the release again (most likely tonight), but if there's anything else we want to get in for 2.1, then I may have to step down.
If Matt is not available I will have the time this week to do a release.
Ralph

Thanks to Matt's RM and coding efforts over the weekend, we went through three RCs and found and resolved a slew of issues.
Thanks Matt once again.
It looks like Matt added the shutdown hook he had discussed and other OSGi related changes. My Apache time is quite limited this week so if anyone else can spend some time on reviewing and polishing 2.1, now is the time.
While the ML and Jira are active with new messages and tickets, it still feels like pushing for 2.1 ASAP is the right thing to do, pending Matt's availability.
Gary
--
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition
Spring Batch in Action
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

--
--
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition
Spring Batch in Action
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
--
--
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition
Spring Batch in Action
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Matt Sicker

2014-10-12 16:05:58 UTC

Permalink

I got a bit busy toward the end of the week, and now I won't have time to
complete the release process.

Post by Ralph Goers
I thought Matt was going to do this. I am not sure what happened.
Ralph
Just FYI, someone just asked for log4j-iostreams functionality on
Stackoverflow
<http://stackoverflow.com/questions/26318295/write-system-out-to-file-with-log4j2/26320693#26320693>.
I realize this is easy for me to say, but shall we release 2.1?

Post by Remko Popma
I looked at the commit emails for the recent changes but nothing caught
my eye; i'm fine with releasing what we have now.
FYI, I started a number of online courses and may have very little time
to work on log4j for the next month or two.
Regards, -Remko
Sent from my iPhone
Not here.
Gary

Post by Matt Sicker
That's what I mean. Any more polishing? Any APIs you forgot to fix
before 2.1 that can be done in a couple hours or so? That sort of thing.

Post by Gary Gregory
I do not think we should add _anything_ for 2.1. If I have an itch
before 2.1 I'll create a branch. Ideally, our time should be spent
polishing.
Gary

Post by Matt Sicker
I should have time to start the release again (most likely tonight),
but if there's anything else we want to get in for 2.1, then I may have to
step down.

Post by Ralph Goers
If Matt is not available I will have the time this week to do a release.
Ralph
Thanks to Matt's RM and coding efforts over the weekend, we went
through three RCs and found and resolved a slew of issues.
Thanks Matt once again.
It looks like Matt added the shutdown hook he had discussed and other
OSGi related changes. My Apache time is quite limited this week so if
anyone else can spend some time on reviewing and polishing 2.1, now is the
time.
While the ML and Jira are active with new messages and tickets, it
still feels like pushing for 2.1 ASAP is the right thing to do, pending
Matt's availability.
Gary
--
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

--
Matt Sicker <***@gmail.com>