Re: [log4j] Separate BOM releases

> On Jul 7, 2023, at 12:07 PM, Piotr P. Karwasz wrote: > > Hi Ralph, > > On Fri, 7 Jul 2023 at 19:00, Ralph Goers wrote: >> ... But maybe I am worrying about nothing and most of the components won’t >> ever be touched. > > That is what I think will happen. Even now most of the components >

Re: [log4j] Separate BOM releases

Spring HAS to use a release train. There are simply too many artifacts. In addition, Spring users would get annoyed at having new Spring releases at random intervals and multiple times per month. This last part is the part I worry about Log4j, although perhaps our ecosystem isn’t large enough (y

Re: [log4j] Separate BOM releases

Hi Ralph, On Fri, 7 Jul 2023 at 19:00, Ralph Goers wrote: > ... But maybe I am worrying about nothing and most of the components won’t > ever be touched. That is what I think will happen. Even now most of the components haven't been touched in years. > This brings up another question. The BOM

Re: [log4j] Separate BOM releases

I kind of like the release train idea (quarterly or some regular cadence); that’s how some of the Spring projects have structured their own releases that combine several unrelated modules. I would be interested in details on what kind of release cadence we’d adopt. > On Jul 7, 2023, at 12:00 PM

RE: [log4j] Separate BOM releases

On 2023/06/23 06:47:35 Volkan Yazıcı wrote: > Piotr and I have been contemplating moving Log4j BOM to its separate > repository with its own release cycle. This need will become even more > pressing as we start breaking down the Log4j modules to their own > repository. > > Ralph and Piotr alrea

Re: [log4j] Separate BOM releases

On Fri, Jun 23, 2023 at 8:49 AM Piotr P. Karwasz wrote: > > Hi Gary, > > On Fri, 23 Jun 2023 at 10:20, Gary Gregory wrote: > > Releasing the BOM every 6 months is not good IMO: It should be released > > every time one of its module is released, making it obvious that all latest > > versions work

Re: [log4j] Separate BOM releases

Hi Gary, On Fri, 23 Jun 2023 at 10:20, Gary Gregory wrote: > Releasing the BOM every 6 months is not good IMO: It should be released > every time one of its module is released, making it obvious that all latest > versions work together _as should be expected_, otherwise we are putting > the work

Re: [log4j] Separate BOM releases

Releasing the BOM every 6 months is not good IMO: It should be released every time one of its module is released, making it obvious that all latest versions work together _as should be expected_, otherwise we are putting the work on our users. If we end up with one repository per jar file, it's go

[log4j] Separate BOM releases

Piotr and I have been contemplating moving Log4j BOM to its separate repository with its own release cycle. This need will become even more pressing as we start breaking down the Log4j modules to their own repository. Ralph and Piotr already exchanged some ideas in #1526