Hello all, As reported in https://issues.apache.org/jira/browse/JAMES-3685 the log4j issue is partially solved.
I am building a new artifact for the 3.6.1 including an upgrade to Log4J 2.16.0, I expect to trigger a (deliberately) short vote later today (give me 3-4h to run the release procedure...). As I am the one doing these release, then my goal is to minimize actions to be taken during my vacations. Better run one release than two... Best regards, Benoit On 14/12/2021 19:28, btell...@apache.org wrote: > Hi, > > I would like to propose a new vote for 3.6.1 release of the Apache James > server. > > You can find: > > - The maven release staged in repository.apache.org as the artifact #1056: > https://repository.apache.org/content/repositories/orgapachejames-1057/ > <https://repository.apache.org/content/repositories/orgapachejames-1056/> > - The changelog for 3.6.1: > https://github.com/chibenwa/james-project/blob/changelog-3.6.1/CHANGELOG.md > <https://github.com/chibenwa/james-project/blob/changelog-3.6.1/CHANGELOG.md> > (to be merged on master) > - The compatibility instructions/upgrade > recommendation: > https://github.com/chibenwa/james-project/blob/changelog-3.6.1/upgrade-instructions.md#361-version > > <https://github.com/chibenwa/james-project/blob/changelog-3.6.1/upgrade-instructions.md#361-version> > > This release is only comprised of bug fixes. > > Voting rules: > - This is a majority approval: this release may not be vetoed. > - A quorum of 3 binding votes is required > - The vote starts at Tuesday 12th of December 2021, 7pm30 UTC+7 > - The vote ends at Friday 15th of December 2021, 7pm30 UTC+7 > > You can answer to it just with +1 and -1. Down-votes may be motivated. > > 3 binding votes are expected move forward on this release. > > Cheers, > > PMC member name > > > --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
