Given we will have several other betas before a GA release, do these issues really constitute a serious blocker? Or they can be addressed in the next beta?
On Thu, 14 Dec 2023 at 21:32, Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > Hi Volkan, > > On Wed, 13 Dec 2023 at 16:26, Volkan Yazıcı <vol...@yazi.ci> wrote: > > > > This is a vote to release the Apache Log4j 3.0.0-beta1. > > > > Website: https://logging.staged.apache.org/log4j > > GitHub: https://github.com/apache/logging-log4j2 > > Commit: c5dbdcfeb0216e1e3e333436e9b4d04cc3b8e6fd > > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j > > Nexus: > > https://repository.apache.org/content/repositories/orgapachelogging-1246 > > Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0 > > > > Please download, test, and cast your votes on this mailing list. > > > > [ ] +1, release the artifacts > > [ ] -1, don't release, because... > > Thanks for preparing the release, unfortunately: > > * The Maven Source Plugin is misconfigured and it publishes **test** > source artifacts. I fixed in in commit > a8dcc55fc37e3a332101dcf0d5833273708b583b, you can cherry-pick it onto > the release branch, > * Since test sources are generated we have reproducibility problems: > the source artifact does not preserve the chmod of each file and some > files have an executable flag... > > Please don't release this. > > Piotr >
