+1
Vincenzo
On Thu, Dec 16, 2021 at 8:44 AM Antoine Duprat wrote:
> +1
>
> Antoine
>
> Le jeu. 16 déc. 2021 à 08:27, btell...@apache.org a
> écrit :
>
> > Hi,
> >
> > I would like to propose a new vote for 3.6.1 release of the Apache James
> > server.
> >
> > This time, as discussed on the
+1
Antoine
Le jeu. 16 déc. 2021 à 08:27, btell...@apache.org a
écrit :
> Hi,
>
> I would like to propose a new vote for 3.6.1 release of the Apache James
> server.
>
> This time, as discussed on the JIRA this includes upgrade to Log4J 2.16.0.
>
> You can find:
>
> - The maven release staged
+1
Our setup of 2nd edition of 3.6.1 including additional patch for Log4J
2.16.0 (which should be equivalent to 3rd edition of 3.6.1) is already
in production for 18 hours.
-
To unsubscribe, e-mail:
+1
On 16/12/2021 14:27, btell...@apache.org wrote:
> Hi,
>
> I would like to propose a new vote for 3.6.1 release of the Apache James
> server.
>
> This time, as discussed on the JIRA this includes upgrade to Log4J 2.16.0.
>
> You can find:
>
> - The maven release staged in repository.apache.org
Hi,
I would like to propose a new vote for 3.6.1 release of the Apache James
server.
This time, as discussed on the JIRA this includes upgrade to Log4J 2.16.0.
You can find:
- The maven release staged in repository.apache.org as the artifact #1058:
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
[
https://issues.apache.org/jira/browse/JAMES-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459925#comment-17459925
]
Benoit Tellier commented on JAMES-3685:
---
+1 but in a separate 3.6.2 release.
One reason is that we
