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 Juhan Aasaru <aa...@gmail.com> on 2021/09/15 13:11:15 UTC
Time for a 3.6.1 release?
Hello!
In recent years James has only had releases 3.1.0, 3.2.0, 3.3.0, 3.4.0,
3.5.0 and 3.6.0.
Since release 3.6.0 this April there has been an effort by the community
(started by https://issues.apache.org/jira/browse/JAMES-3564 ) to identify
bug fixes
from all the new pull requests and after merging them to master branch
also merge them to branch "3.6.x" (visible here:
https://github.com/apache/james-project/tree/3.6.x).
So it is a kind of stabilization branch.
I'm proposing a discussion to create a new release 3.6.1 based on that
branch.
I know it is quite time consuming to create a release but I think it would
be beneficial
for the community as most of the critical bugs in 3.6.0 should be detected
and solved by now.
In case there are any PR-s that should be merged then feel free to add them
to the
Jira task above and I try my best to formulate them as PR-s to 3.6.x branch.
Thanks!
Juhan
Re: Time for a 3.6.1 release?
Posted by "btellier@apache.org" <bt...@apache.org>.
Hello,
I opened https://github.com/apache/james-project/pull/659 for the
MailDir issues which I consider a blocker.
Hopefully I would like to initiate this release before the end of
September, which gives to interested kind contributors a little week to
back-port some of the fixes to master.
Earlier this week I did put together a list of potential back-port
candidates:
https://issues.apache.org/jira/browse/JAMES-3564?focusedCommentId=17415842&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17415842
(Won't quote it here as it is lengthy)
Best regards,
Benoit TELLIER
On 16/09/2021 09:14, btellier@apache.org wrote:
> Hello Julian,
>
> The 3.6.1 is definitly in the pipes.
>
> On 15/09/2021 20:11, Juhan Aasaru wrote:
>> Hello!
>>
>> In recent years James has only had releases 3.1.0, 3.2.0, 3.3.0, 3.4.0,
>> 3.5.0 and 3.6.0.
>> Since release 3.6.0 this April there has been an effort by the community
>> (started by https://issues.apache.org/jira/browse/JAMES-3564 ) to identify
>> bug fixes
>> from all the new pull requests and after merging them to master branch
>> also merge them to branch "3.6.x" (visible here:
>> https://github.com/apache/james-project/tree/3.6.x).
>> So it is a kind of stabilization branch.
>>
>> I'm proposing a discussion to create a new release 3.6.1 based on that
>> branch.
>> I know it is quite time consuming to create a release but I think it would
>> be beneficial
>> for the community as most of the critical bugs in 3.6.0 should be detected
>> and solved by now.
>>
>> In case there are any PR-s that should be merged then feel free to add them
>> to the
>> Jira task above and I try my best to formulate them as PR-s to 3.6.x branch.
> Thanks!
>
> - https://issues.apache.org/jira/browse/JAMES-3647 would benefit from a
> backport.
>
> There remains also issues with MailDir implementation that in my opinion
> would deserve to be fixed prior to a release.
>
> Cheers,
>
> Benoit
>
>> Thanks!
>> Juhan
>>
> ---------------------------------------------------------------------
> 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: Time for a 3.6.1 release?
Posted by "btellier@apache.org" <bt...@apache.org>.
Hello Julian,
The 3.6.1 is definitly in the pipes.
On 15/09/2021 20:11, Juhan Aasaru wrote:
> Hello!
>
> In recent years James has only had releases 3.1.0, 3.2.0, 3.3.0, 3.4.0,
> 3.5.0 and 3.6.0.
> Since release 3.6.0 this April there has been an effort by the community
> (started by https://issues.apache.org/jira/browse/JAMES-3564 ) to identify
> bug fixes
> from all the new pull requests and after merging them to master branch
> also merge them to branch "3.6.x" (visible here:
> https://github.com/apache/james-project/tree/3.6.x).
> So it is a kind of stabilization branch.
>
> I'm proposing a discussion to create a new release 3.6.1 based on that
> branch.
> I know it is quite time consuming to create a release but I think it would
> be beneficial
> for the community as most of the critical bugs in 3.6.0 should be detected
> and solved by now.
>
> In case there are any PR-s that should be merged then feel free to add them
> to the
> Jira task above and I try my best to formulate them as PR-s to 3.6.x branch.
Thanks!
- https://issues.apache.org/jira/browse/JAMES-3647 would benefit from a
backport.
There remains also issues with MailDir implementation that in my opinion
would deserve to be fixed prior to a release.
Cheers,
Benoit
>
> Thanks!
> Juhan
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org