(Just an follow up, not sure if the previous mail went through anyways; to make sure I'll CC Robert and Piotr, please feel free to forward the mail if it didn't make it to the list)
Soft Freeze actually starts March 15th, and from this date on "No large/disruptive changes" are no longer appropiate. This could include a "new upstream release" 1.4.0, not sure if you would categorize the chanes as "large" or "disruptive" (or "risky" to break packages using log4cxx.) Alternatively, I *can* package a RC and then do the final upload after March 15th. (I will be able to reserve e.g March 14th for this) (My least preferred way would be to cherry-pick commits you think must go into Debian13, but that's generally a possibility too.) -- tobi On Sat, Feb 22, 2025 at 10:32:08PM -0500, Robert Middleton wrote: > Should we do a bugfix release of log4cxx soon? We've just had a > release recently, but we have fixed a few bugs with the fuzzing that > was just added. I would like to have a good release for Debian 13. > The soft freeze is April 15, so having a release from our side a few > weeks before that should give it enough time to be pulled in to Debian > 13. Yes, it would be useful to have a release. I guess that there is no SONAME bump; We should aim to be in testing on April 15th, so if a new release, to allow me some days to prepare a new release, it would be nice to have it start of April. Cheers, -- tobi > -Robert Middleton
signature.asc
Description: PGP signature
