Any objections in making the next release 2.7 then? On 18 June 2016 at 17:31, Remko Popma <[email protected]> wrote:
> I was unable to push my fix for LOG4J-1434 yesterday. Will retry soon. > > Sent from my iPhone > > On 2016/06/19, at 5:12, Mikael Ståldal <[email protected]> wrote: > > I think we should fix https://issues.apache.org/jira/browse/LOG4J2-1434 > > On Sat, Jun 18, 2016 at 9:51 PM, Matt Sicker <[email protected]> wrote: > >> Are there any more issues you guys want to finish for 2.6.2 at this time, >> or can we release this soon? >> >> On 12 June 2016 at 23:07, Ralph Goers <[email protected]> wrote: >> >>> I think another point release rather “soonish” is warranted. I’d really >>> like to get a handle on these periodic Jenkins test failures. They may >>> either be something wrong with the test or an actual problem with file >>> rollover. >>> >>> Ralph >>> >>> On Jun 12, 2016, at 7:09 PM, Gary Gregory <[email protected]> >>> wrote: >>> >>> We have quite a bit of activity... :-) Do we plan on releasing a 2.6.2 >>> soonish or waiting for a larger pile to materialize? >>> >>> Gary >>> >>> -- >>> E-Mail: [email protected] | [email protected] >>> 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 <[email protected]> >> > > > > -- > [image: MagineTV] > > *Mikael Ståldal* > Senior software developer > > *Magine TV* > [email protected] > Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com > > Privileged and/or Confidential Information may be contained in this > message. If you are not the addressee indicated in this message > (or responsible for delivery of the message to such a person), you may not > copy or deliver this message to anyone. In such case, > you should destroy this message and kindly notify the sender by reply > email. > > -- Matt Sicker <[email protected]>
