I haven’t started it yet. I just committed a fix for LOG4J2-1250 and am about 
to commit the patch for LOG4J2-950 that was just provided. I also plan to 
update the Log4j 2 web site to link to Log4j 1 so we can get rid of the link on 
the main logging page. I will also provide a link to Log4j 2.3 and update the 
download section for it since it is the last release to support Java 6. Once 
all that is done I plan to start the release. Wife permitting, it should be 
sometime today.

Ralph

> On Jul 4, 2016, at 8:14 AM, Mikael Ståldal <[email protected]> wrote:
> 
> What is the status of the 2.6.2 release?
> 
> On Thu, Jun 30, 2016 at 1:30 AM, Remko Popma <[email protected] 
> <mailto:[email protected]>> wrote:
> Yes. I hope to fix this in the next few days. 
> 
> Sent from my iPhone
> 
> On 2016/06/30, at 8:17, Gary Gregory <[email protected] 
> <mailto:[email protected]>> wrote:
> 
>> I think we need to add https://issues.apache.org/jira/browse/LOG4J2-1452 
>> <https://issues.apache.org/jira/browse/LOG4J2-1452> to the list for 2.6.2. I 
>> see Remko's assigned it to himself :-)
>> 
>> Gary
>> 
>> On Wed, Jun 29, 2016 at 3:26 PM, Gary Gregory <[email protected] 
>> <mailto:[email protected]>> wrote:
>> On Mon, Jun 27, 2016 at 8:18 AM, Ralph Goers <[email protected] 
>> <mailto:[email protected]>> wrote:
>> There is a good chance I’ll do the release build this weekend. Since it is a 
>> holiday weekend I should have more time. But I know there are 1 or 2 other 
>> bugs I want to deal with first.
>> 
>> I'll be around to test if you cut an RC...
>> 
>> Gary 
>> 
>> Ralph
>> 
>> 
>>> On Jun 27, 2016, at 7:15 AM, Leon Finker <[email protected] 
>>> <mailto:[email protected]>> wrote:
>>> 
>>> LOG4J2-1440 it's not super important in my case that empty files are 
>>> rolled. I think someone else requested it. 2.6.2 is good in current state. 
>>> Just eagerly awaiting the release so we can upgrade and use it. Starting 
>>> from 2.6.1 it's impossible to use OnStartupTriggeringPolicy (due to NPE and 
>>> roll on reconfigure).
>>> 
>>> On 2016-06-24 22:46 (-0400), Remko Popma <[email protected] 
>>> <mailto:[email protected]>> wrote: 
>>>> I noticed that Ralph reopened LOG4J2-1440, but is there anything else that 
>>>> we want to include in the 2.6.2 release?
>>>> 
>>>> I'm kind of keen to start on some items scheduled for 2.7. :-)
>>>> 
>>>> Remko 
>>>> 
>>>> Sent from my iPhone
>>>> 
>>>>> On 2016/06/21, at 1:49, Leon Finker <[email protected] 
>>>>> <mailto:[email protected]>> wrote:
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> Can we please start on 2.6.2 release?
>>>>> 
>>>>>> On 2016-06-19 18:37 (-0400), Matt Sicker <[email protected] 
>>>>>> <mailto:[email protected]>> wrote: 
>>>>>> Then it sounds like 2.6.2 is still on the table with the current state of
>>>>>> master (and some other bugs we want to squash for it).
>>>>>> 
>>>>>>> On 19 June 2016 at 07:05, Remko Popma <[email protected] 
>>>>>>> <mailto:[email protected]>> wrote:
>>>>>>> 
>>>>>>> The MessageFactory2 change will not affect existing users, I think the
>>>>>>> issue that Gary raised is more that Semantic Versioning (
>>>>>>> http://semver.org/ <http://semver.org/>) asks that for API changes you 
>>>>>>> increment a different
>>>>>>> part of the version number than for bugfixes.
>>>>>>> 
>>>>>>> Our versioning is not as strict as semver though, so sometimes we need 
>>>>>>> to
>>>>>>> briefly discuss which part of the version number to increase. In this 
>>>>>>> case
>>>>>>> I think we agreed that the next version will be 2.6.2.
>>>>>>> 
>>>>>>> On Sun, Jun 19, 2016 at 5:44 PM, Mikael Ståldal 
>>>>>>> <[email protected] <mailto:[email protected]>
>>>>>>>> wrote:
>>>>>>> 
>>>>>>>> I think that the MessageFactory2 fix was designed to not affect 
>>>>>>>> existing
>>>>>>>> users.
>>>>>>>> 
>>>>>>>> On Sun, Jun 19, 2016 at 10:37 AM, Mikael Ståldal <
>>>>>>>> [email protected] <mailto:[email protected]>> wrote:
>>>>>>>> 
>>>>>>>>> The direct option to ConsoleAppender won't be noticed by users unless
>>>>>>>>> they enable it.
>>>>>>>>> 
>>>>>>>>>> On Sun, Jun 19, 2016 at 2:02 AM, Matt Sicker <[email protected] 
>>>>>>>>>> <mailto:[email protected]>> wrote:
>>>>>>>>>> 
>>>>>>>>>> I haven't merged AsyncAppender yet.
>>>>>>>>>> 
>>>>>>>>>> On 18 June 2016 at 18:59, Ralph Goers <[email protected] 
>>>>>>>>>> <mailto:[email protected]>>
>>>>>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>>> I don’t think so. The change you made to the AsyncAppender 
>>>>>>>>>>> won’t be
>>>>>>>>>>> noticed by users unless they configure it.
>>>>>>>>>>> 
>>>>>>>>>>> I’m not sure what the impact is on the MessageFactory2 change.
>>>>>>>>>>> 
>>>>>>>>>>> Ralph
>>>>>>>>>>> 
>>>>>>>>>>> On Jun 18, 2016, at 4:55 PM, Matt Sicker <[email protected] 
>>>>>>>>>>> <mailto:[email protected]>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> Should we cherry pick the two changes in question into a separate
>>>>>>>>>>> branch that we merge back into the 2.7 code?
>>>>>>>>>>> 
>>>>>>>>>>> It might be worth discussing at some point maintaining a sort of
>>>>>>>>>>> "previous release" branch for basic bugfixes.
>>>>>>>>>>> 
>>>>>>>>>>>> On 18 June 2016 at 18:45, Remko Popma <[email protected] 
>>>>>>>>>>>> <mailto:[email protected]>> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>> Any other issues that we want to fix for 2.6.2?
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> On Sunday, 19 June 2016, Ralph Goers <[email protected] 
>>>>>>>>>>>> <mailto:[email protected]>>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>>> I’d rather do another point release.  I am targeting a few bugs 
>>>>>>>>>>>>> that
>>>>>>>>>>>>> need to be fixed. I’d rather 2.7 contain more new stuff, such 
>>>>>>>>>>>>> as enhancing
>>>>>>>>>>>>> the Rolling file appenders.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> I guess I am more a fan of V.R.M.P than I am of
>>>>>>>>>>>>> Version.Release.Patch.  If that was the case we would be talking 
>>>>>>>>>>>>> about
>>>>>>>>>>>>> 2.0.6.2 vs 2.0.7.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Ralph
>>>>>>>>>>>>> 
>>>>>>>>>>>>> On Jun 18, 2016, at 3:37 PM, Matt Sicker <[email protected] 
>>>>>>>>>>>>> <mailto:[email protected]>> wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Any objections in making the next release 2.7 then?
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On 18 June 2016 at 17:31, Remko Popma <[email protected] 
>>>>>>>>>>>>>> <mailto:[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] <mailto:[email protected]>>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> I think we should fix
>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/LOG4J2-1434 
>>>>>>>>>>>>>> <https://issues.apache.org/jira/browse/LOG4J2-1434>
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On Sat, Jun 18, 2016 at 9:51 PM, Matt Sicker <[email protected] 
>>>>>>>>>>>>>> <mailto:[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] <mailto:[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] <mailto:[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] <mailto:[email protected]> 
>>>>>>>>>>>>>>>> | [email protected] <mailto:[email protected]>
>>>>>>>>>>>>>>>> Java Persistence with Hibernate, Second Edition
>>>>>>>>>>>>>>>> <http://www.manning.com/bauer3/ 
>>>>>>>>>>>>>>>> <http://www.manning.com/bauer3/>>
>>>>>>>>>>>>>>>> JUnit in Action, Second Edition
>>>>>>>>>>>>>>>> <http://www.manning.com/tahchiev/ 
>>>>>>>>>>>>>>>> <http://www.manning.com/tahchiev/>>
>>>>>>>>>>>>>>>> Spring Batch in Action <http://www.manning.com/templier/ 
>>>>>>>>>>>>>>>> <http://www.manning.com/templier/>>
>>>>>>>>>>>>>>>> Blog: http://garygregory.wordpress.com 
>>>>>>>>>>>>>>>> <http://garygregory.wordpress.com/>
>>>>>>>>>>>>>>>> Home: http://garygregory.com/ <http://garygregory.com/>
>>>>>>>>>>>>>>>> Tweet! http://twitter.com/GaryGregory 
>>>>>>>>>>>>>>>> <http://twitter.com/GaryGregory>
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Matt Sicker <[email protected] <mailto:[email protected]>>
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> [image: MagineTV]
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> *Mikael Ståldal*
>>>>>>>>>>>>>> Senior software developer
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> *Magine TV*
>>>>>>>>>>>>>> [email protected] <mailto:[email protected]>
>>>>>>>>>>>>>> Grev Turegatan 3  | 114 46 Stockholm, Sweden  |   www.magine.com 
>>>>>>>>>>>>>> <http://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] <mailto:[email protected]>>
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> --
>>>>>>>>>>> Matt Sicker <[email protected] <mailto:[email protected]>>
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> --
>>>>>>>>>> Matt Sicker <[email protected] <mailto:[email protected]>>
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> --
>>>>>>>>> [image: MagineTV]
>>>>>>>>> 
>>>>>>>>> *Mikael Ståldal*
>>>>>>>>> Senior software developer
>>>>>>>>> 
>>>>>>>>> *Magine TV*
>>>>>>>>> [email protected] <mailto:[email protected]>
>>>>>>>>> Grev Turegatan 3  | 114 46 Stockholm, Sweden  |   www.magine.com 
>>>>>>>>> <http://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.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> --
>>>>>>>> [image: MagineTV]
>>>>>>>> 
>>>>>>>> *Mikael Ståldal*
>>>>>>>> Senior software developer
>>>>>>>> 
>>>>>>>> *Magine TV*
>>>>>>>> [email protected] <mailto:[email protected]>
>>>>>>>> Grev Turegatan 3  | 114 46 Stockholm, Sweden  |   www.magine.com 
>>>>>>>> <http://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] <mailto:[email protected]>>
>>>>> 
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [email protected] 
>>>>> <mailto:[email protected]>
>>>>> For additional commands, e-mail: [email protected] 
>>>>> <mailto:[email protected]>
>>>>> 
>>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected] 
>>> <mailto:[email protected]>
>>> For additional commands, e-mail: [email protected] 
>>> <mailto:[email protected]>
>> 
>> 
>> 
>> -- 
>> E-Mail: [email protected] <mailto:[email protected]> | 
>> [email protected]  <mailto:[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 <http://garygregory.wordpress.com/> 
>> Home: http://garygregory.com/ <http://garygregory.com/>
>> Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
>> 
>> 
>> -- 
>> E-Mail: [email protected] <mailto:[email protected]> | 
>> [email protected]  <mailto:[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 <http://garygregory.wordpress.com/> 
>> Home: http://garygregory.com/ <http://garygregory.com/>
>> Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
> 
> 
> -- 
>  
> 
> Mikael Ståldal
> Senior software developer 
> 
> Magine TV
> [email protected] <mailto:[email protected]>    
> Grev Turegatan 3  | 114 46 Stockholm, Sweden  |   www.magine.com  
> <http://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.  
>  

Reply via email to