Mailman Suite 3.0rc1 awaiting an upstream fix

[Sumana Harihareswara]

At the PyCon sprint last week, we made a lot of progress towards a 3.0
release and we discussed next steps. I'm very glad so many of us could
make it and pitch in.

The 3.0rc1 depends on a new Falcon release because there's a bugfix
awaiting release in Falcon that fixes a blocker bug for us:
https://bugs.launchpad.net/postorius/+bug/1444504 Once that's out, we
can put out a release candidate.

In order to release 3.0.0 final, we need core native releases for all 5
components of the Mailman suite, with tested installation instructions
and with all the components tagged, tested, and on PyPI. We'd also like
some infrastructure and workflow improvements before we do that -- for
one thing, we ought to set up continuous integration to run our
automated tests on every merge. We will probably request a CI server/VM
from the Python Software Foundation. We could actually set up CI for
HyperKitty (and probably our other components as well) right away using
the (no guarantee of uptime/service level) Jenkins installation at
http://jenkins.cloud.fedoraproject.org/ if someone followed the
instructions at
https://fedoraproject.org/wiki/Jenkins@infra#Can_I_add_my_project_to_Jenk...
and add ticket to https://fedorahosted.org/fedora-infrastructure/ . We
need to have an i18n setup and I've agreed to take lead on that. And
there's further potential wrangling around Launchpad, branches, Bazaar,
Git, etc. that I'll write up tomorrow.

Hope this helps keep everyone up to date.
-- 
Sumana Harihareswara
http://brainwane.net

[Mailman-Developers] Mailman Suite 3.0rc1 awaiting an upstream fix

[Pierre-Yves Chibon]

On Mon, Apr 20, 2015 at 10:53:09AM -0400, Sumana Harihareswara wrote:
>  At the PyCon sprint last week, we made a lot of progress towards a
> 3.0
>  release and we discussed next steps. I'm very glad so many of us could
>  make it and pitch in.
>  
>  The 3.0rc1 depends on a new Falcon release because there's a bugfix
>  awaiting release in Falcon that fixes a blocker bug for us:
>  https://bugs.launchpad.net/postorius/+bug/1444504 Once that's out, we
>  can put out a release candidate.
>  
>  In order to release 3.0.0 final, we need core native releases for all 5
>  components of the Mailman suite, with tested installation instructions
>  and with all the components tagged, tested, and on PyPI. We'd also like
>  some infrastructure and workflow improvements before we do that -- for
>  one thing, we ought to set up continuous integration to run our
>  automated tests on every merge. We will probably request a CI server/VM
>  from the Python Software Foundation. We could actually set up CI for
>  HyperKitty (and probably our other components as well) right away using
>  the (no guarantee of uptime/service level) Jenkins installation at
>  http://jenkins.cloud.fedoraproject.org/ if someone followed the
>  instructions at
>  https://fedoraproject.org/wiki/Jenkins@infra#Can_I_add_my_project_to_Jenk...
>  and add ticket to https://fedorahosted.org/fedora-infrastructure/ . We
>  need to have an i18n setup and I've agreed to take lead on that. And
>  there's further potential wrangling around Launchpad, branches, Bazaar,
>  Git, etc. that I'll write up tomorrow. 
We are (as in Patrick is) currently working on getting a Fedora 22 builder added
to the jenkins instance so that we have a python 3.4 available for you folks if
you so desire :)


Pierre

[Mailman-Developers] Mailman Suite 3.0rc1 awaiting an upstream fix

[Aurelien Bompard]

>  We are (as in Patrick is) currently working on getting a Fedora 22
> builder added
>  to the jenkins instance so that we have a python 3.4 available for you folks if
>  you so desire :) 

Fedora 21 has Python 3.4, so that would be enough.

A.

[Mailman-Developers] Mailman Suite 3.0rc1 awaiting an upstream fix

[Pierre-Yves Chibon]

On Mon, Apr 20, 2015 at 08:19:29PM +0200, Aurelien Bompard wrote:
>  > We are (as in Patrick is) currently working on getting a Fedora
> 22 builder added
>  > to the jenkins instance so that we have a python 3.4 available for you folks if
>  > you so desire :)
>  
>  
>  Fedora 21 has Python 3.4, so that would be enough. 
That is true, but currently we only have a F20 builder, but good to know that if
we do not manage to get the F22 one running, we can also try getting a F21 one
up.

Thanks,
Pierre