Yes, I'm building with log4j 2.16 now.
Will BadApple a few tests, yes..

Jan

> 14. des. 2021 kl. 10:39 skrev Uwe Schindler <[email protected]>:
> 
> I think we should update log4j to 2.16.0:
> 
> Reason: It has all JNDI and expansion of ${...} in log messages disabled. So 
> we also prevent that people enable this with buggy logging configs.
> 
> Uwe
> 
> -----
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> https://www.thetaphi.de
> eMail: [email protected]
> 
>> -----Original Message-----
>> From: Adrien Grand <[email protected]>
>> Sent: Tuesday, December 14, 2021 8:57 AM
>> To: Lucene Dev <[email protected]>
>> Subject: Re: Lucene/Solr 8.11.1 release
>> 
>> Jan, if you remember the names of the tests that fail, can you
>> annotate them with @BadApple so that they will not fail when building
>> new RCs or future 8.11 patch releases?
>> 
>> 
>> On Tue, Dec 14, 2021 at 8:41 AM Jan Høydahl <[email protected]>
>> wrote:
>>> 
>>> I've had one run which passed tests, but then it failed signing due to me 
>>> using
>> Ant 1.10. After that I had 2 runs with one test failure each.. This beast is 
>> hard
>> to please.
>>> Will continue with Ant 1.9 until there is a passing build and then announce
>> RC1.
>>> 
>>> Jan
>>> 
>>> 14. des. 2021 kl. 01:08 skrev Jan Høydahl <[email protected]>:
>>> 
>>> +1
>>> 
>>> Feel free to merge it if you feel an itch. Then I'll git pull before next 
>>> build
>> attempt.
>>> 
>>> Jan
>>> 
>>> 14. des. 2021 kl. 01:00 skrev Mike Drob <[email protected]>:
>>> 
>>> There's been a log4j 2.16 release as well, should we pick that one up if 
>>> your
>> next attempt fails?
>>> 
>>> https://logging.apache.org/log4j/2.x/changes-report.html#a2.16.0
>>> 
>>> On Mon, Dec 13, 2021 at 5:58 PM Jan Høydahl <[email protected]>
>> wrote:
>>>> 
>>>> Currently running 4th attempt at making buildAndPushRelease.py happy.
>> Always different tests failing...
>>>> 
>>>> Jan
>>>> 
>>>> 13. des. 2021 kl. 21:00 skrev David Smiley <[email protected]>:
>>>> 
>>>> Looks good; thanks Jan!
>>>> 
>>>> ~ David Smiley
>>>> Apache Lucene/Solr Search Developer
>>>> http://www.linkedin.com/in/davidwsmiley
>>>> 
>>>> 
>>>> On Mon, Dec 13, 2021 at 9:34 AM Jan Høydahl <[email protected]>
>> wrote:
>>>>> 
>>>>> Including Lucene dev as well.
>>>>> 
>>>>> As I see no Lucene level bug fixes for 8.11.1, I have prepared an "empty"
>> release announcement:
>> https://cwiki.apache.org/confluence/display/LUCENE/ReleaseNote8_11_1
>>>>> Please edit as you see fit.
>>>>> 
>>>>> The Solr announcement is slightly updated, proof-read welcome
>> https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote8_11_1
>>>>> 
>>>>> There are now 18 CHANGES entries for Solr:
>> https://github.com/apache/lucene-solr/blob/branch_8_11/solr/CHANGES.txt
>>>>> 
>>>>> Jan
>>>>> 
>>>>>> 13. des. 2021 kl. 02:24 skrev Jan Høydahl <[email protected]>:
>>>>>> 
>>>>>> There seems to be no open blockers for 8.11.1, so I'll proceed with RC1
>> soon.
>>>>>> Shout out if you want me to wait for a specific important bugfix.
>>>>>> 
>>>>>> Please also review the Release Notes at
>> https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote8_11_1
>>>>>> 
>>>>>> Jan
>>>>>> 
>>>>>>> 8. des. 2021 kl. 02:48 skrev Timothy Potter <[email protected]>:
>>>>>>> 
>>>>>>> agreed! thanks for stepping up to be the RM Jan ;-)
>>>>>>> 
>>>>>>> On Tue, Dec 7, 2021 at 6:05 PM Jan Høydahl <[email protected]>
>> wrote:
>>>>>>>> 
>>>>>>>> Hi,
>>>>>>>> 
>>>>>>>> Solr has 13 bug fixes lined up in branch_8_11 already. Lucene has no
>> changes.
>>>>>>>> Now that Lucene 9.0 is out the door (congrats!), let's do the 8.11.1
>> release.
>>>>>>>> 
>>>>>>>> I volunteer as RM and propose a first RC on Monday 13th. That should
>> allow some time to merge any last bug fixes both for Lucene and Solr.
>>>>>>>> Please feel free to backport bug fixes with your own judgement (no
>> new features please). If you are uncertain whether a backport is "safe", 
>> please
>> raise a question here.
>>>>>>>> 
>>>>>>>> I'll re-enable Jenkins for branch_8_11 now. Commits that fix or
>> @BadApples unstable tests highly appreciated.
>>>>>>>> 
>>>>>>>> Jan
>>>>>>>> 
>>>>>>>> 
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: [email protected]
>>>>>>>> For additional commands, e-mail: [email protected]
>>>>>>>> 
>>>>>>> 
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: [email protected]
>>>>>>> For additional commands, e-mail: [email protected]
>>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [email protected]
>>>>> For additional commands, e-mail: [email protected]
>>>>> 
>>>> 
>>> 
>>> 
>> 
>> 
>> --
>> Adrien
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to