You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Volkan Yazıcı <vo...@gmail.com> on 2020/10/13 12:31:40 UTC
Re: Ramp down for Log4j 2.14.0 release (Was: JsonTemplateLayout is
ready to be shipped!)
Ralph, are there any updates from your side? Are you still swamped with
$daywork? Will you be able to spare some time for a new release?
On Wed, Sep 23, 2020 at 10:41 AM Volkan Yazıcı <vo...@gmail.com>
wrote:
> AFAIC, the latest release-2.x build on GitHub Actions
> <https://github.com/apache/logging-log4j2/actions/runs/267532184> looks
> good to me. There are still certain tests that are failing on Windows and
> OSX. The OSX ones are pretty much random; sometimes they do succeed,
> sometimes they do fail. Regarding Windows-specific ones, they also look
> superficial to me; a couple of "... because it is being used by another
> process" hiccups and some other stuff. Yesterday evening, I introduced log4j2.junit.fileCleanerSleepPeriodMillis
> property to take effect in AbstractFileCleaner and updated Windows build
> on GitHub Actions configuration accordingly. Extending the sleep period of AbstractFileCleaner
> for Windows builds helped to mitigate certain test failures, I think. Today
> I plan to spend some time fixing ReconfigurationDeadlockTest failures.
>
> In conclusion, the current state of release-2.x branch looks good to me
> for a release -- at least, it is not worse than the one in the previous 2.x
> release. Please let me know if I am missing something.
>
>
Re: Ramp down for Log4j 2.14.0 release (Was: JsonTemplateLayout is
ready to be shipped!)
Posted by Matt Sicker <bo...@gmail.com>.
I may have time this Friday to prepare a release if everything is in
releasable order.
On Tue, 13 Oct 2020 at 07:31, Volkan Yazıcı <vo...@gmail.com> wrote:
>
> Ralph, are there any updates from your side? Are you still swamped with
> $daywork? Will you be able to spare some time for a new release?
>
> On Wed, Sep 23, 2020 at 10:41 AM Volkan Yazıcı <vo...@gmail.com>
> wrote:
>
> > AFAIC, the latest release-2.x build on GitHub Actions
> > <https://github.com/apache/logging-log4j2/actions/runs/267532184> looks
> > good to me. There are still certain tests that are failing on Windows and
> > OSX. The OSX ones are pretty much random; sometimes they do succeed,
> > sometimes they do fail. Regarding Windows-specific ones, they also look
> > superficial to me; a couple of "... because it is being used by another
> > process" hiccups and some other stuff. Yesterday evening, I introduced log4j2.junit.fileCleanerSleepPeriodMillis
> > property to take effect in AbstractFileCleaner and updated Windows build
> > on GitHub Actions configuration accordingly. Extending the sleep period of AbstractFileCleaner
> > for Windows builds helped to mitigate certain test failures, I think. Today
> > I plan to spend some time fixing ReconfigurationDeadlockTest failures.
> >
> > In conclusion, the current state of release-2.x branch looks good to me
> > for a release -- at least, it is not worse than the one in the previous 2.x
> > release. Please let me know if I am missing something.
> >
> >
--
Matt Sicker <bo...@gmail.com>
Re: Ramp down for Log4j 2.14.0 release (Was: JsonTemplateLayout is
ready to be shipped!)
Posted by Ralph Goers <ra...@dslextreme.com>.
Yes, but there is a light at the end of the tunnel. The component I am building at work has taken more than twice as long as I expected.
We have gotten a few issues recently that look really important to look into. I’d like to at least have them looked into before we cut the release.
Ralph
> On Oct 13, 2020, at 5:31 AM, Volkan Yazıcı <vo...@gmail.com> wrote:
>
> Ralph, are there any updates from your side? Are you still swamped with
> $daywork? Will you be able to spare some time for a new release?
>
> On Wed, Sep 23, 2020 at 10:41 AM Volkan Yazıcı <vo...@gmail.com>
> wrote:
>
>> AFAIC, the latest release-2.x build on GitHub Actions
>> <https://github.com/apache/logging-log4j2/actions/runs/267532184> looks
>> good to me. There are still certain tests that are failing on Windows and
>> OSX. The OSX ones are pretty much random; sometimes they do succeed,
>> sometimes they do fail. Regarding Windows-specific ones, they also look
>> superficial to me; a couple of "... because it is being used by another
>> process" hiccups and some other stuff. Yesterday evening, I introduced log4j2.junit.fileCleanerSleepPeriodMillis
>> property to take effect in AbstractFileCleaner and updated Windows build
>> on GitHub Actions configuration accordingly. Extending the sleep period of AbstractFileCleaner
>> for Windows builds helped to mitigate certain test failures, I think. Today
>> I plan to spend some time fixing ReconfigurationDeadlockTest failures.
>>
>> In conclusion, the current state of release-2.x branch looks good to me
>> for a release -- at least, it is not worse than the one in the previous 2.x
>> release. Please let me know if I am missing something.
>>
>>