Bumping the autoconfig xml format to support multiple incoming servers.

Ludovic Hirlimann ludovic at hirlimann.net
Fri Mar 26 17:31:15 UTC 2010

 On 26/03/10 18:17, Blake Winton wrote:
> In https://bugzilla.mozilla.org/show_bug.cgi?id=532590#c64, BenB
> suggested that he has a patch (albeit without tests) in
> https://bugzilla.mozilla.org/show_bug.cgi?id=531267 to clean up our
> XML handling in various ways.  Notably, by allowing us to have more
> than one incomingServer.
> The current Thunderbird code doesn't handle that case, so if we start
> adding alternate incomingServers (i.e. IMAP and POP), people on
> Thunderbird versions 3.0.0 to 3.0.4 will stop recognizing the config
> files.  That's bad.
> My proposal was to add an extra element which would hide the
> additional incomingServers from TB 3.0.  On the upside, that meant we
> wouldn't need to bump the XML format, but on the downside it feels a
> little like an ad-hoc solution to a larger problem.
> Ben's counter-proposal is to copy the configs from
> https://live.mozillamessaging.com/autoconfig/ to
> https://live.mozillamessaging.com/autoconfig/v3.1/ and just add the
> extra incomingServers.  We would maintain the (current) V3.0 format
> files manually until it gets annoying, at which point we can write a
> script to convert the v3.1 format files to v3.0, and have them be
> maintained that way.
> I think this sounds like a reasonable way forward, but wanted to open
> it up to the wider communities before going too far down this path.
> Thoughts?
How about versionning the xml format - not based on the client. version
0 goes for 3.0.x.
Version 1 which is the change you are proposing , dealst with version
Xxxx -> YYYY etc ....

As for the maintainance - , when we EOL one product and that product was
the last one using version z ,we just remove version z from svn. Which
we'll need to do carefully for people distributing Tb in linux distros
for instance and offering longer support than we do.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 291 bytes
Desc: OpenPGP digital signature
URL: <http://mail.mozilla.org/pipermail/tb-planning/attachments/20100326/681b5784/attachment.sig>

More information about the tb-planning mailing list