Re: [Mailman-Developers] Setting up installation to test own changes
On 10/24/2016 07:00 AM, Ana Cutillas wrote:
we at Systers had a student over summer work on some features and we would like to put those in a server and do some testing.
I was thinking of using the mailman bundler and then changing the source files (she only did changes to postorius). Would that work? Or should we do it differently?
The recommended development setup is at <https://wiki.list.org/DEV/SetupDevEnvironment>. Mailman bundler is not recommended because it doesn't install the current development branches.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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
participants (2)
-
Mark Sapiro -
Stephen J. Turnbull