Bumping the autoconfig xml format to support multiple incoming servers.
bwinton at mozillamessaging.com
Fri Mar 26 17:50:18 UTC 2010
On 10-03-26 13:31 , Ludovic Hirlimann wrote:
> How about versioning the xml format - not based on the client. version
> 0 goes for 3.0.x.
> Version 1 which is the change you are proposing, deals with version
> Xxxx -> YYYY etc ....
So, it's poorly communicated, but the xml format wasn't intended to be
tied to the client version. It looks like only bluewin.ch and
cgl.ucsf.edu have a version listed, and they can be changed or removed.
As a nit, since we've already got code out there dealing with the
current version, we should probably call it version 1.0, and this next
version could be 1.1 or 2.0.
> 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.
I thought we wouldn't keep the old format in svn, but would keep it
around on the server, being automatically generated from the newest
version for a while.
We do have stats on how many people hit various urls on the autoconfig
site, so we could keep the old formats around until they haven't been
hit for, say, 6 months.
More information about the tb-planning