Re: Ramp down for Log4j 2.14.0 release (Was: JsonTemplateLayout is ready to be shipped!)

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

Re: Ramp down for Log4j 2.14.0 release (Was: JsonTemplateLayout is ready to be shipped!)

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ı 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

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ı wrote: > AFAIC, the latest release-2.x build on GitHub Actions >

Re: Ramp down for Log4j 2.14.0 release (Was: JsonTemplateLayout is ready to be shipped!)

Thanks for figuring out the Windows errors! The unit test migration doesn’t need to be completed before the next release, so that’s not a hold up. On Wed, Sep 23, 2020 at 03:40 Volkan Yazıcı wrote: > AFAIC, the latest release-2.x build on GitHub Actions > >

Ramp down for Log4j 2.14.0 release (Was: JsonTemplateLayout is ready to be shipped!)

AFAIC, the latest release-2.x build on GitHub Actions 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. Regard

Re: JsonTemplateLayout is ready to be shipped!

I've reverted a couple errant commits that introduced test failures. Besides the RollingDirectSizeTimeNewDirectoryTest test, the remaining failures are Windows-specific. On Sat, 12 Sep 2020 at 13:06, Ralph Goers wrote: > > Gary, I think you misunderstood. It may be another week before I start the

Re: JsonTemplateLayout is ready to be shipped!

Gary, I think you misunderstood. It may be another week before I start the release. Yes, the build issues need to be addressed. I was laying out my process before starting a release. I am suggesting that there should be time to fix the build and look at PRs and Jira issues before the release is

Re: JsonTemplateLayout is ready to be shipped!

Summary of failing tests: * JsonWriterTest has some linkage errors only showing up on Windows? * SpringLookupTest is consistently failing only on Windows * EquinoxLoadApiBundleTest is failing everywhere with some class signing error (related to that OSGi dependency update I mentioned) * RollingDir

Re: JsonTemplateLayout is ready to be shipped!

I think focusing on fixing the build should come before considering bringing in PRs or Jira issues. I think Matt stated we don't get a clean build ATM? Gary On Sat, Sep 12, 2020, 13:55 Ralph Goers wrote: > Yeah, I rely mostly on the automation but I run the build on my Mac > several times befor

Re: JsonTemplateLayout is ready to be shipped!

Yeah, I rely mostly on the automation but I run the build on my Mac several times before a release and if any of them fail I wouldn’t even start the release process. I still am working on my $dayjob project and would still want to take a look at open Jira issues before starting the release. I wo

Re: JsonTemplateLayout is ready to be shipped!

Seems like one of the things we need to do before the release candidate is get all the tests passing again. I'll look more into any test failures introduced from my JUnit 5 refactoring. We do have test failures related to OSGi at the moment due to a dependency update, though that might be due to in

Re: JsonTemplateLayout is ready to be shipped!

It is no problem. I have been heads down trying to get something done for work. Should be soon though. Ralph > On Sep 11, 2020, at 4:40 AM, Volkan Yazıcı wrote: > > Hey Ralph! This is your friendly reminder for the pending 2.x release. > (Apologies for the inconvenience.) > >> On Thu, Aug 27

Re: JsonTemplateLayout is ready to be shipped!

I can try to prepare the next release this weekend. I need to fix some unit tests as it is, so I'll take a look at what's in flight to see if anything else needs merging before making the RC. On Fri, 11 Sep 2020 at 06:40, Volkan Yazıcı wrote: > > Hey Ralph! This is your friendly reminder for the

Re: JsonTemplateLayout is ready to be shipped!

Hey Ralph! This is your friendly reminder for the pending 2.x release. (Apologies for the inconvenience.) On Thu, Aug 27, 2020 at 3:55 PM Apache wrote: > No, you are not expected to do anything else. While anyone can be the > release manager, typically I have been doing them. They take a fair am

Re: JsonTemplateLayout is ready to be shipped!

I should add that I also promised to help get the Log4Net site deployed and to move the web site off of the CMS, so I may do those before creating a release. Ralph > On Aug 27, 2020, at 6:54 AM, Apache wrote: > > No, you are not expected to do anything else. While anyone can be the release >

Re: JsonTemplateLayout is ready to be shipped!

No, you are not expected to do anything else. While anyone can be the release manager, typically I have been doing them. They take a fair amount of time so I typically start them on a weekend when I have enough time. Ralph > On Aug 27, 2020, at 6:14 AM, Volkan Yazıcı wrote: > > Would anybod

Re: JsonTemplateLayout is ready to be shipped!

Would anybody mind giving some indication on an ETA, please? Or am I expected to do anything else further? On Tue, Aug 25, 2020 at 1:59 PM Volkan Yazıcı wrote: > Yes, you read the subject right! I will appreciate it if people can spare > some time on skimming through the change set one last time

JsonTemplateLayout is ready to be shipped!

Yes, you read the subject right! I will appreciate it if people can spare some time on skimming through the change set one last time regarding JTL. So... When are we gonna cut the ribbon for the upcoming 2.x release?