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 Tellier Benoit <bt...@apache.org> on 2022/03/02 03:44:29 UTC
[VOTE] Apache James release 3.7.0
Hi,
I would like to propose a new vote for 3.7.0 release of the Apache James
server.
You can find:
- The maven release staged in repository.apache.org as the
artifact #1062:
https://repository.apache.org/content/repositories/orgapachejames-1062/
- The changelog for
3.7.0:
https://github.com/apache/james-project/blob/master/CHANGELOG.md#unreleased
- Changes to our doc and the website:
https://github.com/apache/james-project/pull/900
- Release artifacts are uploaded to ASF dowloads.
This release introduces some major bug fixes, stability enhancements and
some cool additional components and features!
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 Wednesday 2nd of March 2022, 10am UTC+7
- The vote ends at Wednesday 9th of March 2022, 10am 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,
Benoit TELLIER
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [VOTE] Apache James release 3.7.0
Posted by "Otto, Karsten Andreas" <Ka...@akquinet.de.INVALID>.
+1
On 02.03.22 4:44 AM, Tellier Benoit wrote:
> Hi,
>
> I would like to propose a new vote for 3.7.0 release of the Apache James
> server.
>
> You can find:
>
> - The maven release staged in repository.apache.org as the
> artifact #1062:
> https://repository.apache.org/content/repositories/orgapachejames-1062/
> - The changelog for
> 3.7.0:
> https://github.com/apache/james-project/blob/master/CHANGELOG.md#unreleased
> - Changes to our doc and the website:
> https://github.com/apache/james-project/pull/900
> - Release artifacts are uploaded to ASF dowloads.
>
> This release introduces some major bug fixes, stability enhancements and
> some cool additional components and features!
>
> 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 Wednesday 2nd of March 2022, 10am UTC+7
> - The vote ends at Wednesday 9th of March 2022, 10am 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,
>
> Benoit TELLIER
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
Re: [VOTE] Apache James release 3.7.0
Posted by Rene Cordier <rc...@apache.org>.
+1,
Rene.
On 02/03/2022 10:44, Tellier Benoit wrote:
> Hi,
>
> I would like to propose a new vote for 3.7.0 release of the Apache James
> server.
>
> You can find:
>
> - The maven release staged in repository.apache.org as the
> artifact #1062:
> https://repository.apache.org/content/repositories/orgapachejames-1062/
> - The changelog for
> 3.7.0:
> https://github.com/apache/james-project/blob/master/CHANGELOG.md#unreleased
> - Changes to our doc and the website:
> https://github.com/apache/james-project/pull/900
> - Release artifacts are uploaded to ASF dowloads.
>
> This release introduces some major bug fixes, stability enhancements and
> some cool additional components and features!
>
> 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 Wednesday 2nd of March 2022, 10am UTC+7
> - The vote ends at Wednesday 9th of March 2022, 10am 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,
>
> Benoit TELLIER
>
> ---------------------------------------------------------------------
> 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: [VOTE] Apache James release 3.7.0
Posted by Vincenzo Gianferrari Pini <vi...@gocloud.it>.
+1
Vincenzo
___________________________
Ing. Vincenzo Gianferrari Pini
Il Mer 2 Mar 2022, 04:44 Tellier Benoit <bt...@apache.org> ha scritto:
> Hi,
>
> I would like to propose a new vote for 3.7.0 release of the Apache James
> server.
>
> You can find:
>
> - The maven release staged in repository.apache.org as the
> artifact #1062:
> https://repository.apache.org/content/repositories/orgapachejames-1062/
> - The changelog for
> 3.7.0:
> https://github.com/apache/james-project/blob/master/CHANGELOG.md#unreleased
> - Changes to our doc and the website:
> https://github.com/apache/james-project/pull/900
> - Release artifacts are uploaded to ASF dowloads.
>
> This release introduces some major bug fixes, stability enhancements and
> some cool additional components and features!
>
> 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 Wednesday 2nd of March 2022, 10am UTC+7
> - The vote ends at Wednesday 9th of March 2022, 10am 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,
>
> Benoit TELLIER
>
> ---------------------------------------------------------------------
> 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: Sv: [VOTE] Apache James release 3.7.0
Posted by Andreas Joseph Krogh <an...@visena.com>.
På onsdag 02. mars 2022 kl. 11:10:04, skrev Tellier Benoit <btellier@apache.org
<ma...@apache.org>>:
Ok.
I created https://issues.apache.org/jira/browse/JAMES-3718
<https://issues.apache.org/jira/browse/JAMES-3718> to make sure this do not get
forgotten...
Regards,
Benoit
Excellent, thanks!
--
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: Sv: [VOTE] Apache James release 3.7.0
Posted by Tellier Benoit <bt...@apache.org>.
Ok.
I created https://issues.apache.org/jira/browse/JAMES-3718 to make sure
this do not get forgotten...
Regards,
Benoit
Le 02/03/2022 à 15:21, Andreas Joseph Krogh a écrit :
> På onsdag 02. mars 2022 kl. 09:10:16, skrev Tellier Benoit
> <btellier@apache.org <ma...@apache.org>>:
>
> Hello Andreas,
>
>
> Sadly a release is a poor moment to discuss the perimeter.
>
> Running a release process 'just' to come to the vote took me over
> 12 hours, I am personally upset wasting my time running multiple
> releases for nothing. By the way, except for 3.5.0 releasing is a
> burdon that I did carry mostly by my own for several years
> already, for free to the community. I would be glad we better
> share this responsibility.
>
> My mindset (we can discuss this) is that the project should always
> be on a releasable state. Additions according to the will of
> contributors should not compete with the release milestone. That
> is, users and contributors can open tickets and code contribution
> when they encounter the need, independently from releases. When we
> release, what is ready is included, what is not ready / not done
> will go for next release.
>
> In this case, the contributors would have had likely carried the
> task out if we had a JIRA ticket saying "Upgrade the MIME4J code a
> new version to include unreleased changes". The ticket do not
> exist thus it was not carried out. I encourage you to create such
> a ticket. It would then be included in 3.7.1 / 3.8.0.
>
>
> Finally I sent an email one week ago, seeking consensus toward
> such a release. Raising your voice during consensus seeking phases
> rather than on votes would surely help mitigate such conflicts. CF
> https://www.mail-archive.com/server-dev@james.apache.org/msg71619.html
>
> Regards,
>
> Benoit
>
> Please express your concerns on the email I sent one week before
> explaining I was about to release cf
>
> No problem, I didn't mean to hold up the release, sorry for the noise.
> It's no big deal for us to include a custom build of mime4j from master.
>
>
>
> +1 for releasing.
>
>
>
> --
> *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: Sv: [VOTE] Apache James release 3.7.0
Posted by Andreas Joseph Krogh <an...@visena.com>.
På onsdag 02. mars 2022 kl. 09:10:16, skrev Tellier Benoit <btellier@apache.org
<ma...@apache.org>>:
Hello Andreas,
Sadly a release is a poor moment to discuss the perimeter.
Running a release process 'just' to come to the vote took me over 12 hours, I
am personally upset wasting my time running multiple releases for nothing. By
the way, except for 3.5.0 releasing is a burdon that I did carry mostly by my
own for several years already, for free to the community. I would be glad we
better share this responsibility.
My mindset (we can discuss this) is that the project should always be on a
releasable state. Additions according to the will of contributors should not
compete with the release milestone. That is, users and contributors can open
tickets and code contribution when they encounter the need, independently from
releases. When we release, what is ready is included, what is not ready / not
done will go for next release.
In this case, the contributors would have had likely carried the task out if
we had a JIRA ticket saying "Upgrade the MIME4J code a new version to include
unreleased changes". The ticket do not exist thus it was not carried out. I
encourage you to create such a ticket. It would then be included in 3.7.1 /
3.8.0.
Finally I sent an email one week ago, seeking consensus toward such a release.
Raising your voice during consensus seeking phases rather than on votes would
surely help mitigate such conflicts. CF
https://www.mail-archive.com/server-dev@james.apache.org/msg71619.html
<https://www.mail-archive.com/server-dev@james.apache.org/msg71619.html>
Regards,
Benoit
Please express your concerns on the email I sent one week before explaining I
was about to release cf
No problem, I didn't mean to hold up the release, sorry for the noise. It's no
big deal for us to include a custom build of mime4j from master.
+1 for releasing.
--
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: Sv: [VOTE] Apache James release 3.7.0
Posted by Tellier Benoit <bt...@apache.org>.
Hello Andreas,
Sadly a release is a poor moment to discuss the perimeter.
Running a release process 'just' to come to the vote took me over 12
hours, I am personally upset wasting my time running multiple releases
for nothing. By the way, except for 3.5.0 releasing is a burdon that I
did carry mostly by my own for several years already, for free to the
community. I would be glad we better share this responsibility.
My mindset (we can discuss this) is that the project should always be on
a releasable state. Additions according to the will of contributors
should not compete with the release milestone. That is, users and
contributors can open tickets and code contribution when they encounter
the need, independently from releases. When we release, what is ready is
included, what is not ready / not done will go for next release.
In this case, the contributors would have had likely carried the task
out if we had a JIRA ticket saying "Upgrade the MIME4J code a new
version to include unreleased changes". The ticket do not exist thus it
was not carried out. I encourage you to create such a ticket. It would
then be included in 3.7.1 / 3.8.0.
Finally I sent an email one week ago, seeking consensus toward such a
release. Raising your voice during consensus seeking phases rather than
on votes would surely help mitigate such conflicts. CF
https://www.mail-archive.com/server-dev@james.apache.org/msg71619.html
Regards,
Benoit
Please express your concerns on the email I sent one week before
explaining I was about to release cf
Le 02/03/2022 à 14:32, Andreas Joseph Krogh a écrit :
> På onsdag 02. mars 2022 kl. 04:44:29, skrev Tellier Benoit
> <btellier@apache.org <ma...@apache.org>>:
>
> Hi,
>
> I would like to propose a new vote for 3.7.0 release of the Apache
> James
> server.
> […]
>
>
>
> I'd like to see a release of mime4j first then depend on that for
> 3.7.0, as it got some important fixes (for us at least).
>
>
>
> --
> *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
Sv: [VOTE] Apache James release 3.7.0
Posted by Andreas Joseph Krogh <an...@visena.com>.
På onsdag 02. mars 2022 kl. 04:44:29, skrev Tellier Benoit <btellier@apache.org
<ma...@apache.org>>:
Hi,
I would like to propose a new vote for 3.7.0 release of the Apache James
server.
[…]
I'd like to see a release of mime4j first then depend on that for 3.7.0, as it
got some important fixes (for us at least).
--
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: [VOTE] Apache James release 3.7.0
Posted by Tellier Benoit <bt...@apache.org>.
+1
Le 02/03/2022 à 10:44, Tellier Benoit a écrit :
> Hi,
>
> I would like to propose a new vote for 3.7.0 release of the Apache James
> server.
>
> You can find:
>
> - The maven release staged in repository.apache.org as the
> artifact #1062:
> https://repository.apache.org/content/repositories/orgapachejames-1062/
> - The changelog for
> 3.7.0:
> https://github.com/apache/james-project/blob/master/CHANGELOG.md#unreleased
> - Changes to our doc and the website:
> https://github.com/apache/james-project/pull/900
> - Release artifacts are uploaded to ASF dowloads.
>
> This release introduces some major bug fixes, stability enhancements and
> some cool additional components and features!
>
> 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 Wednesday 2nd of March 2022, 10am UTC+7
> - The vote ends at Wednesday 9th of March 2022, 10am 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,
>
> Benoit TELLIER
>
> ---------------------------------------------------------------------
> 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
[RESULT] [VOTE] Apache James release 3.7.0
Posted by Tellier Benoit <bt...@apache.org>.
|Hi all, I am happy to announce you the vote for the 3.7.0 release did
succeed. The release received 5 positive votes, 3 of them being binding.
Thanks to all contributors, developers and committers who made this
possible! In the coming hours, I will finalize the release process,
namely: - Publish the maven artifacts - Upgrade the download page and
the (old) website - Announce the release Cheers, PMC member name|
Le 07/03/2022 à 15:09, Antoine Duprat a écrit :
> +1
>
> Cheers,
> Antoine
>
> Le mer. 2 mars 2022 à 04:44, Tellier Benoit <bt...@apache.org> a écrit :
>
>> Hi,
>>
>> I would like to propose a new vote for 3.7.0 release of the Apache James
>> server.
>>
>> You can find:
>>
>> - The maven release staged in repository.apache.org as the
>> artifact #1062:
>> https://repository.apache.org/content/repositories/orgapachejames-1062/
>> - The changelog for
>> 3.7.0:
>> https://github.com/apache/james-project/blob/master/CHANGELOG.md#unreleased
>> - Changes to our doc and the website:
>> https://github.com/apache/james-project/pull/900
>> - Release artifacts are uploaded to ASF dowloads.
>>
>> This release introduces some major bug fixes, stability enhancements and
>> some cool additional components and features!
>>
>> 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 Wednesday 2nd of March 2022, 10am UTC+7
>> - The vote ends at Wednesday 9th of March 2022, 10am 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,
>>
>> Benoit TELLIER
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-dev-help@james.apache.org
>>
>>
Re: [VOTE] Apache James release 3.7.0
Posted by Antoine Duprat <ad...@apache.org>.
+1
Cheers,
Antoine
Le mer. 2 mars 2022 à 04:44, Tellier Benoit <bt...@apache.org> a écrit :
> Hi,
>
> I would like to propose a new vote for 3.7.0 release of the Apache James
> server.
>
> You can find:
>
> - The maven release staged in repository.apache.org as the
> artifact #1062:
> https://repository.apache.org/content/repositories/orgapachejames-1062/
> - The changelog for
> 3.7.0:
> https://github.com/apache/james-project/blob/master/CHANGELOG.md#unreleased
> - Changes to our doc and the website:
> https://github.com/apache/james-project/pull/900
> - Release artifacts are uploaded to ASF dowloads.
>
> This release introduces some major bug fixes, stability enhancements and
> some cool additional components and features!
>
> 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 Wednesday 2nd of March 2022, 10am UTC+7
> - The vote ends at Wednesday 9th of March 2022, 10am 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,
>
> Benoit TELLIER
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>