You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "btellier@apache.org" <bt...@apache.org> on 2021/12/03 01:29:46 UTC
Call for vote: Apache James 3.6.1
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-1056/
- The changelog for 3.6.1:
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
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 Friday 3rd of December 2021, 8am30 UTC+7
- The vote ends at Friday 10th of December 2021, 8am30 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Call for vote: Apache James 3.6.1
Posted by Vincenzo Gianferrari Pini <vi...@gocloud.it>.
+1
Vincenzo

___________________________
Ing. Vincenzo Gianferrari Pini
Liquidatore - GoCloud S.r.l
Sede legale: Via Larga 15, 20122 Milano (MI)
Cel. +39-3939837493
fax: +39-02-25514302
<vi...@gocloud.eu>
https://google.com/+VincenzoGianferrariPiniGoCloud
https://www.linkedin.com/in/vgianferrari
http://www.gocloud.eu
Il Ven 3 Dic 2021, 02:30 btellier@apache.org <bt...@apache.org> ha
scritto:
> 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-1056/
> - The changelog for 3.6.1:
> 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
>
> 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 Friday 3rd of December 2021, 8am30 UTC+7
> - The vote ends at Friday 10th of December 2021, 8am30 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-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
--
Il presente messaggio ed i suoi allegati sono confidenziali in ragione
della loro natura professionale e, in ogni caso, non accessibili al
pubblico. Nel caso in cui il presente messaggio sia ricevuto da soggetto
diverso dal suo diretto destinatario, si prega di darne immediata notizia
all'indirizzo email *amministrazione@gocloud.it
<ma...@gocloud.it>* e di procedere immediatamente alla
distruzione dello stesso e dei suoi allegati, da effettuarsi senza copiarne
o rivelarne ad alcuno il contenuto. Grazie per la collaborazione.
This
e-mail and any attachments thereto are confidential and may be covered by
legal professional privilege or otherwise protected from disclosure. If you
are not the intended recipient, please notify us immediately by email to
the address _amministrazione@gocloud.it <ma...@gocloud.it>
and then immediately destroy this message and any attachments from your
system, without copying or disclosing the contents to any other person.
Thank you for your co-operation._
Re: Call for vote: Apache James 3.6.1
Posted by Rene Cordier <rc...@apache.org>.
+1,
Rene.
On 03/12/2021 08:29, btellier@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-1056/
> - The changelog for 3.6.1:
> 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
>
> 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 Friday 3rd of December 2021, 8am30 UTC+7
> - The vote ends at Friday 10th of December 2021, 8am30 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-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Call for vote: Apache James 3.6.1
Posted by "btellier@apache.org" <bt...@apache.org>.
+1
On 03/12/2021 08:29, btellier@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-1056/
> - The changelog for 3.6.1:
> 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
>
> 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 Friday 3rd of December 2021, 8am30 UTC+7
> - The vote ends at Friday 10th of December 2021, 8am30 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-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Call for vote: Apache James 3.6.1
Posted by Andreas Joseph Krogh <an...@visena.com>.
På fredag 03. desember 2021 kl. 11:25:39, skrev btellier@apache.org
<ma...@apache.org> <btellier@apache.org <ma...@apache.org>>:
Hello Andreas,
I encourage you to take a formal position on the release (+1, -1, etc...)
regarding this vote.
I think it is a very good thing that members of the community feels concerned
by the content of the 3.6.1 release. Code contributions are welcomed on the
3.6.x release line, there were sadly not a lot of community activity there. If
required (rejected vote) I can devote myself to re-tag a 3.6.1 release. Or
other committers should feel free to carry over this task (release guide here:
https://james.staged.apache.org/james-project/3.7.0/community/release.html
<https://james.staged.apache.org/james-project/3.7.0/community/release.html> ):
help welcome here!
While we are at it, as you show interest in this 3.6.1 release, do you have
plans to address the various bugs mentioned in [2]
https://issues.apache.org/jira/browse/JAMES-3564?focusedCommentId=17415842&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17415842
<https://issues.apache.org/jira/browse/JAMES-3564?focusedCommentId=17415842&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17415842>
that would benefit from a backport to 3.6.x? There are surely there things
more critical that the 2 MIME4J enhancements you are pointing to... We likely
should be active on backports prior to releases. This would ease everybody
life. And avoid costly re-tags that are just a waste of time.
Also, in October board report, we mentioned both the 3.6.1 and 3.7.0 releases
that ideally should be carried out ideally before January board report. So,
ideally, I'd like to tag both releases before 15th december for a release date
~22nd dec.
To be fair I am more interested by the 3.7.0 release that ships awesome
improvements and performance enhancements, but I consider 3.6.1 fixed critical
bugfixes, and as 3.7.0 drops maildir, we need to offer decent options for
potential maildir users out there (hence me pushing 3.6.1 further).
Best regards,
Benoit TELLIER
I agree, get 3.6.1 out the door and maybe have mime4j updated for the 3.7.0
release.
Regarding the issues you linked to there are only a few issues impacting us as
we're using JAMES as an IMAP-server only, with some custom glue-code to make it
work with our storage-architecture, which uses JPA, using a custom data-model.
We will have a look at the issues and see if there's anything we can
fix/improve.
So - +1 from me:-)
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas@visena.com <ma...@visena.com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>
Re: Call for vote: Apache James 3.6.1
Posted by "btellier@apache.org" <bt...@apache.org>.
Hello Andreas,
I encourage you to take a formal position on the release (+1, -1,
etc...) regarding this vote.
I think it is a very good thing that members of the community feels
concerned by the content of the 3.6.1 release. Code contributions are
welcomed on the 3.6.x release line, there were sadly not a lot of
community activity there. If required (rejected vote) I can devote
myself to re-tag a 3.6.1 release. Or other committers should feel free
to carry over this task (release guide here:
https://james.staged.apache.org/james-project/3.7.0/community/release.html
): help welcome here!
While we are at it, as you show interest in this 3.6.1 release, do you
have plans to address the various bugs mentioned in [2]
https://issues.apache.org/jira/browse/JAMES-3564?focusedCommentId=17415842&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17415842
that would benefit from a backport to 3.6.x? There are surely there
things more critical that the 2 MIME4J enhancements you are pointing
to... We likely should be active on backports prior to releases. This
would ease everybody life. And avoid costly re-tags that are just a
waste of time.
Also, in October board report, we mentioned both the 3.6.1 and 3.7.0
releases that ideally should be carried out ideally before January board
report. So, ideally, I'd like to tag both releases before 15th december
for a release date ~22nd dec.
To be fair I am more interested by the 3.7.0 release that ships awesome
improvements and performance enhancements, but I consider 3.6.1 fixed
critical bugfixes, and as 3.7.0 drops maildir, we need to offer decent
options for potential maildir users out there (hence me pushing 3.6.1
further).
Best regards,
Benoit TELLIER
On 03/12/2021 16:42, Andreas Joseph Krogh wrote:
> På fredag 03. desember 2021 kl. 09:43:32, skrev btellier@apache.org
> <ma...@apache.org> <btellier@apache.org
> <ma...@apache.org>>:
>
> Hello Andreas,
>
> I spent literally a day running the release, I would have had
> enjoyed having such kind of feedbacks earlier, for instance when I
> first spoke about my will to move forward with 3.6.1 (15/09/2021
> [1]) and then asked for help for the backports (16/09/2021 [2]).
>
> [1]
> https://www.mail-archive.com/server-dev@james.apache.org/msg71028.html
> [2]
> https://issues.apache.org/jira/browse/JAMES-3564?focusedCommentId=17415842&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17415842
>
> What changeset would you consider critical for a MIME4J upgrade?
> On 3.6.x we shall minimize changes in order to provide stability
> and only target bugfixes.
>
> I'm not personally interested in 3.6.x backports, thus I would
> appreciate the community to involve more on this topic.
>
>
> I understnad, but these issues:
>
> https://github.com/apache/james-mime4j/pull/65
> <https://github.com/apache/james-mime4j/pull/65>
> https://github.com/apache/james-mime4j/pull/66
> <https://github.com/apache/james-mime4j/pull/66>
>
> …were not merged/fixed at the time. Now that they are merged it
> becomes relevant.
>
> --
> *Andreas Joseph Krogh*
> CTO / Partner - Visena AS
> Mobile: +47 909 56 963
> andreas@visena.com <ma...@visena.com>
> www.visena.com <https://www.visena.com>
> <https://www.visena.com>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
Re: Call for vote: Apache James 3.6.1
Posted by Andreas Joseph Krogh <an...@visena.com>.
På fredag 03. desember 2021 kl. 09:43:32, skrev btellier@apache.org
<ma...@apache.org> <btellier@apache.org <ma...@apache.org>>:
Hello Andreas,
I spent literally a day running the release, I would have had enjoyed having
such kind of feedbacks earlier, for instance when I first spoke about my will
to move forward with 3.6.1 (15/09/2021 [1]) and then asked for help for the
backports (16/09/2021 [2]).
[1] https://www.mail-archive.com/server-dev@james.apache.org/msg71028.html
<https://www.mail-archive.com/server-dev@james.apache.org/msg71028.html>
[2]
https://issues.apache.org/jira/browse/JAMES-3564?focusedCommentId=17415842&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17415842
<https://issues.apache.org/jira/browse/JAMES-3564?focusedCommentId=17415842&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17415842>
What changeset would you consider critical for a MIME4J upgrade? On 3.6.x we
shall minimize changes in order to provide stability and only target bugfixes.
I'm not personally interested in 3.6.x backports, thus I would appreciate the
community to involve more on this topic.
I understnad, but these issues:
https://github.com/apache/james-mime4j/pull/65
<https://github.com/apache/james-mime4j/pull/65>
https://github.com/apache/james-mime4j/pull/66
<https://github.com/apache/james-mime4j/pull/66>
…were not merged/fixed at the time. Now that they are merged it becomes
relevant.
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas@visena.com <ma...@visena.com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>
Re: Call for vote: Apache James 3.6.1
Posted by "btellier@apache.org" <bt...@apache.org>.
Hello Andreas,
I spent literally a day running the release, I would have had enjoyed
having such kind of feedbacks earlier, for instance when I first spoke
about my will to move forward with 3.6.1 (15/09/2021 [1]) and then asked
for help for the backports (16/09/2021 [2]).
[1] https://www.mail-archive.com/server-dev@james.apache.org/msg71028.html
[2]
https://issues.apache.org/jira/browse/JAMES-3564?focusedCommentId=17415842&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17415842
What changeset would you consider critical for a MIME4J upgrade? On
3.6.x we shall minimize changes in order to provide stability and only
target bugfixes.
I'm not personally interested in 3.6.x backports, thus I would
appreciate the community to involve more on this topic.
Regards,
Benoit
On 03/12/2021 15:27, Andreas Joseph Krogh wrote:
> On Friday 03. December 2021 at 02:29:46, btellier@apache.org
> <ma...@apache.org> <btellier@apache.org
> <ma...@apache.org>> wrote:
>
> Hi,
>
> I would like to propose a new vote for 3.6.1 release of the Apache
> James
> server.
> […]
>
>
> Is it possible to release MIME4J 0.8.7 and have JAMES-3.6.1 depende on
> that?
>
> --
> *Andreas Joseph Krogh*
> CTO / Partner - Visena AS
> Mobile: +47 909 56 963
> andreas@visena.com <ma...@visena.com>
> www.visena.com <https://www.visena.com>
> <https://www.visena.com>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
Re: Call for vote: Apache James 3.6.1
Posted by Andreas Joseph Krogh <an...@visena.com>.
On Friday 03. December 2021 at 02:29:46, btellier@apache.org
<ma...@apache.org> <btellier@apache.org <ma...@apache.org>>
wrote:
Hi,
I would like to propose a new vote for 3.6.1 release of the Apache James
server.
[…]
Is it possible to release MIME4J 0.8.7 and have JAMES-3.6.1 depende on that?
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas@visena.com <ma...@visena.com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>
Re: Call for vote: Apache James 3.6.1
Posted by Antoine Duprat <ad...@apache.org>.
+1
Antoine
Le ven. 3 déc. 2021 à 02:30, btellier@apache.org <bt...@apache.org> a
écrit :
> 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-1056/
> - The changelog for 3.6.1:
> 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
>
> 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 Friday 3rd of December 2021, 8am30 UTC+7
> - The vote ends at Friday 10th of December 2021, 8am30 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-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
Re: Call for vote: Apache James 3.6.1
Posted by Eugen Stan <eu...@netdava.com>.
+1 for 3.6.1
--
Eugen Stan
+40770 941 271 / https://www.netdava.com