[Pkg-mailman-hackers] Re: [mm-deb] RFD: How to proceed from 2.1.4-3?

[Siggy Brentrup]

--GZVR6ND4mMseVXL/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 06, 2004 at 01:45:44AM +0200, Tollef Fog Heen wrote:
> * Siggy Brentrup=20
> | BTW, apart from Tollef reporting upstream plans, I find no mention
> | of any MM version beyond 2.0.5 in the bug trail.  So we don't even
> | know for sure that setup made the transition to 2.1.

> If you run with the web server on the NFS client, it ought to work,
> but I haven't checked whether that code is still the same in 2.1.
> Would surprise me a bit if it weren't though.

Just to name some considerations that come to mind at a 1st glance:
 - both machines must run identical Python versions (cPickle),
 - mm_cfg.py must be in sync,
 - language templates must be in sync,
all of which aren't supported by current dpkg and friends and must be
guaranteed by the administrator anyway.

On 2nd thought: while the submitter's approach of separating SMTP and
HTTP traffic to different machines looks appealing at first, IMHO
moving all ML traffic to the web server (if not dedicating a machine
to MM) is a lot easier to administer.

To summarize: I'm against that split.

Thanks
 . Siggy

ps: 2.1.4-3 is in testing, no new bug reports since the upload :-)

--GZVR6ND4mMseVXL/
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAcpBz94B/SGO8KQcRAmckAJ9hV8N3mX15cAxxZ/2IqB8weZdugwCgiKfn
39rThVJYHG7+rB8X4SEYfkA=
=03cz
-----END PGP SIGNATURE-----

--GZVR6ND4mMseVXL/--