[Mailman-Developers] Setting up installation to test own changes
Stephen J. Turnbull
turnbull.stephen.fw at u.tsukuba.ac.jp
Tue Oct 25 06:38:57 EDT 2016
Mark Sapiro writes:
> Mailman bundler is not recommended because it doesn't install the
> current development branches.
Mailman 3.1 is "close" to release (how close is for Barry, Florian and
Aurelian to say, but the improvements over 3.0 in the dev branches are
substantial). I strongly (as co-mentor :-) recommend using the dev
branches.
I'm not sure how far bundler has been updated, but the kind of issue
you are likely to run into is, for example,
<https://gitlab.com/mailman/mailman-hyperkitty/issues/10>
This is a problem with the environment that tox sets up for standalone
testing, not with interoperability of current Mailman components with
each other. However, as stated in
<https://gitlab.com/mailman/mailman/issues/181>
this kind of thing is generally not going to get timely fixes in static
bundles.
Aside to devs: I think we should toxify the procedure at
<https://wiki.list.org/DEV/SetupDevEnvironment>, and allow
specification of a ref tuple for the mailman components.
Steve
More information about the Mailman-Developers
mailing list