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 btell...@apache.org > <mailto:btell...@apache.org> <btell...@apache.org > <mailto:btell...@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 > andr...@visena.com <mailto:andr...@visena.com> > www.visena.com <https://www.visena.com> > <https://www.visena.com> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org > For additional commands, e-mail: server-dev-h...@james.apache.org
