Re: [log4j] Releasing Log4j `3.0.0`

2023-11-29 Thread Matt Sicker
I’m good with a beta release to come soon. I’m still working on a branch to fix up the remaining SPI updates to avoid guessing at ClassLoaders, but that isn’t required for a beta release. As for the branches, if 2.x was made into 3.0, then main would be 4.0, and where would that leave us? Back

Re: [log4j] Releasing Log4j `3.0.0`

2023-11-28 Thread Volkan Yazıcı
Okay. I will do the next beta release sometime this week. We can do more as we see fit. On Tue, 28 Nov 2023 at 15:59, Ralph Goers wrote: > I do not understand what my email provider has against Volkan. Once again > I did not receive his email. > > Looking at the archive I see you want to

Re: [log4j] Releasing Log4j `3.0.0`

2023-11-28 Thread Ralph Goers
I do not understand what my email provider has against Volkan. Once again I did not receive his email. Looking at the archive I see you want to release 3.0.0 in February. That may be possible but that isn’t exactly what was discussed in the last video meeting we had. The meeting notes are at

Re: [log4j] Releasing Log4j `3.0.0`

2023-11-28 Thread Ralph Goers
> On Nov 28, 2023, at 7:21 AM, Gary Gregory wrote: > > I'm OK with either direction for merges for anything between 2.x and 3.x > branches for now and certainly until 3.x makes it out as a release. I won't > argue for or against either. > > As a semi aside, in Commons, I circumvented the

Re: [log4j] Releasing Log4j `3.0.0`

2023-11-28 Thread Gary Gregory
I'm OK with either direction for merges for anything between 2.x and 3.x branches for now and certainly until 3.x makes it out as a release. I won't argue for or against either. As a semi aside, in Commons, I circumvented the whole JPMS garbage, its split module horror show for tests by letting

Re: [log4j] Releasing Log4j `3.0.0`

2023-11-28 Thread Piotr P. Karwasz
Hi Volkan, On Tue, 28 Nov 2023 at 11:20, Volkan Yazıcı wrote: > *Personal remark:* I am against releasing `3.0.0` from `main`. `2.x` > changes that didn't go into `main` are titanic. `main` also contains > several incomplete code, doc, or both. I support the idea of forking `3.x` > from `2.x`,

[log4j] Releasing Log4j `3.0.0`

2023-11-28 Thread Volkan Yazıcı
I plan to work on `main` until February, finalize recycler implementation, carry out whatever improvement I can, and release `3.0.0`. *If you have any objections with this plan, or if you have things to do on `main` and you cannot comply with this schedule, etc., let's discuss.* I want to agree