You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Gary Gregory <ga...@gmail.com> on 2018/12/07 17:47:34 UTC
What's left for 2.11.2?
Hi All:
What are the pending issues left we want for 2.11.2?
Gary
Re: What's left for 2.11.2?
Posted by Gary Gregory <ga...@gmail.com>.
On Fri, Dec 7, 2018 at 2:21 PM Gary Gregory <ga...@gmail.com> wrote:
> 2.x is blue (why not green Jenkins? whyyyyy?)
>
https://builds.apache.org/view/L/view/Logging/job/Log4j%202%202.x/
I'll look at 3.x...
Gary
>
>
> On Fri, Dec 7, 2018 at 11:46 AM Ralph Goers <ra...@dslextreme.com>
> wrote:
>
>> I am really waiting for confirmation that the fix for LOG4J2-1906 is
>> working correctly. You initially had an error on Windows but it sounds like
>> it went away. Jenkins failed once on it but hasn’t failed since. The report
>> of LOG4J2-2517 is related but since I can’t reproduce that it isn’t a
>> blocker.
>>
>> However, the latest Jenkins builds have been failing due to some of the
>> tests you added not passing. Those have to be fixed before a release can
>> occur.
>>
>> Ralph
>>
>> > On Dec 7, 2018, at 10:47 AM, Gary Gregory <ga...@gmail.com>
>> wrote:
>> >
>> > Hi All:
>> >
>> > What are the pending issues left we want for 2.11.2?
>> >
>> > Gary
>>
>>
>>
Re: What's left for 2.11.2?
Posted by Carter Kozak <ck...@apache.org>.
Red-green color blindness is fairly common as well :-)
On Fri, Dec 7, 2018 at 5:10 PM Matt Sicker <bo...@gmail.com> wrote:
>
> On Fri, 7 Dec 2018 at 15:28, Gary Gregory <ga...@gmail.com> wrote:
>
> > 2.x is blue (why not green Jenkins? whyyyyy?)
> >
>
> From Wikipedia:
> Japanese traffic signals mostly follow the same rule except that the "go"
> signals are referred to as 青 (blue
> <https://en.wikipedia.org/wiki/Blue%E2%80%93green_distinction_in_language#Japanese>),
> which they historically were in fact, but this caused complications with
> the international "green for go" rule, so [29]
> <https://en.wikipedia.org/wiki/Traffic_light#cite_note-30> in 1973 a decree
> was issued that the "go" light should be changed to the bluest possible hue
> of green, thus making it factually greener without having to change the
> name from 青(blue) to 緑(green)
>
> (Original author of Jenkins is Japanese)
>
> --
> Matt Sicker <bo...@gmail.com>
Re: What's left for 2.11.2?
Posted by Matt Sicker <bo...@gmail.com>.
On Fri, 7 Dec 2018 at 15:28, Gary Gregory <ga...@gmail.com> wrote:
> 2.x is blue (why not green Jenkins? whyyyyy?)
>
From Wikipedia:
Japanese traffic signals mostly follow the same rule except that the "go"
signals are referred to as 青 (blue
<https://en.wikipedia.org/wiki/Blue%E2%80%93green_distinction_in_language#Japanese>),
which they historically were in fact, but this caused complications with
the international "green for go" rule, so [29]
<https://en.wikipedia.org/wiki/Traffic_light#cite_note-30> in 1973 a decree
was issued that the "go" light should be changed to the bluest possible hue
of green, thus making it factually greener without having to change the
name from 青(blue) to 緑(green)
(Original author of Jenkins is Japanese)
--
Matt Sicker <bo...@gmail.com>
Re: What's left for 2.11.2?
Posted by Gary Gregory <ga...@gmail.com>.
2.x is blue (why not green Jenkins? whyyyyy?)
On Fri, Dec 7, 2018 at 11:46 AM Ralph Goers <ra...@dslextreme.com>
wrote:
> I am really waiting for confirmation that the fix for LOG4J2-1906 is
> working correctly. You initially had an error on Windows but it sounds like
> it went away. Jenkins failed once on it but hasn’t failed since. The report
> of LOG4J2-2517 is related but since I can’t reproduce that it isn’t a
> blocker.
>
> However, the latest Jenkins builds have been failing due to some of the
> tests you added not passing. Those have to be fixed before a release can
> occur.
>
> Ralph
>
> > On Dec 7, 2018, at 10:47 AM, Gary Gregory <ga...@gmail.com>
> wrote:
> >
> > Hi All:
> >
> > What are the pending issues left we want for 2.11.2?
> >
> > Gary
>
>
>
Re: What's left for 2.11.2?
Posted by Ralph Goers <ra...@dslextreme.com>.
Yeah, I installed it in VMWare Fusion. Windows 10 didn’t run well at all in VirtualBox on my laptop. However, I didn’t pay for a license and don’t intend to so it will expire after 3 months. As I recall that won’t cripple anything though.
Ralph
> On Dec 7, 2018, at 12:16 PM, Matt Sicker <bo...@gmail.com> wrote:
>
> Speaking of Windows, I recently installed Parallels for testing things in
> Windows (generally Windows-specific bugs), so going forward, I'll try to
> verify our releases in multiple operating systems.
>
> On Fri, 7 Dec 2018 at 12:46, Ralph Goers <ra...@dslextreme.com> wrote:
>
>> I am really waiting for confirmation that the fix for LOG4J2-1906 is
>> working correctly. You initially had an error on Windows but it sounds like
>> it went away. Jenkins failed once on it but hasn’t failed since. The report
>> of LOG4J2-2517 is related but since I can’t reproduce that it isn’t a
>> blocker.
>>
>> However, the latest Jenkins builds have been failing due to some of the
>> tests you added not passing. Those have to be fixed before a release can
>> occur.
>>
>> Ralph
>>
>>> On Dec 7, 2018, at 10:47 AM, Gary Gregory <ga...@gmail.com>
>> wrote:
>>>
>>> Hi All:
>>>
>>> What are the pending issues left we want for 2.11.2?
>>>
>>> Gary
>>
>>
>>
>
> --
> Matt Sicker <bo...@gmail.com>
Re: What's left for 2.11.2?
Posted by Matt Sicker <bo...@gmail.com>.
Speaking of Windows, I recently installed Parallels for testing things in
Windows (generally Windows-specific bugs), so going forward, I'll try to
verify our releases in multiple operating systems.
On Fri, 7 Dec 2018 at 12:46, Ralph Goers <ra...@dslextreme.com> wrote:
> I am really waiting for confirmation that the fix for LOG4J2-1906 is
> working correctly. You initially had an error on Windows but it sounds like
> it went away. Jenkins failed once on it but hasn’t failed since. The report
> of LOG4J2-2517 is related but since I can’t reproduce that it isn’t a
> blocker.
>
> However, the latest Jenkins builds have been failing due to some of the
> tests you added not passing. Those have to be fixed before a release can
> occur.
>
> Ralph
>
> > On Dec 7, 2018, at 10:47 AM, Gary Gregory <ga...@gmail.com>
> wrote:
> >
> > Hi All:
> >
> > What are the pending issues left we want for 2.11.2?
> >
> > Gary
>
>
>
--
Matt Sicker <bo...@gmail.com>
Re: What's left for 2.11.2?
Posted by Ralph Goers <ra...@dslextreme.com>.
I am really waiting for confirmation that the fix for LOG4J2-1906 is working correctly. You initially had an error on Windows but it sounds like it went away. Jenkins failed once on it but hasn’t failed since. The report of LOG4J2-2517 is related but since I can’t reproduce that it isn’t a blocker.
However, the latest Jenkins builds have been failing due to some of the tests you added not passing. Those have to be fixed before a release can occur.
Ralph
> On Dec 7, 2018, at 10:47 AM, Gary Gregory <ga...@gmail.com> wrote:
>
> Hi All:
>
> What are the pending issues left we want for 2.11.2?
>
> Gary