2.0rc7 -> 2.0 in two weeks
joon at radleys.co.za
Wed Apr 30 18:47:24 CEST 2008
We do a version check on the Kolab-XML and any version we do not understand
Toltec rejects. I thought that was the whole point of putting the version in
the Kolab-XML object :)
Radley Network Technologies CC
Cell: +27 (0)83 368 8557
Fax: +27 (0)12 998 4346
E-mail: joon at radleys.co.za
> -----Original Message-----
> From: kolab-format-bounces at kolab.org [mailto:kolab-format-
> bounces at kolab.org] On Behalf Of Bernhard Reiter
> Sent: Wednesday, April 30, 2008 4:24 PM
> To: kolab-format at kolab.org
> Cc: ludwig at intevation.de; Joon Radley
> Subject: Re: 2.0rc7 -> 2.0 in two weeks
> Hi Joon,
> On Friday 18 April 2008 17:12, Bernhard Reiter wrote:
> > Hmmm, actually there were a few minor changes over the time, so I
> > think it would be reasonable to stick with the idea of using 2.0 now.
> > Otherwise we could decouple the version number of the type from the
> > version number of the specification and just keep the "1.0" until we
> > hit an incompatible change. I tend to at least upgrade to "2.0".
> > Shouldn't be a large problem as implementor would have considered
> > "feature" for a while.
> > What do you all think?
> we (Ludwig) did a quick test with
> KDE Kolab Client Proko2, enterprise35, Horde and Toltec 2.2.0 (we
> happend to have this on one testing machine).
> s/<event version="1.0" >/<event version="2.0" >
> s/<contact version=1.0" >/<contact version="2.0">
> the only problem was there with Toltec which did not display the
> Joon, can you confirm?
> If so, this would be an argument for keeping "1.0" in the upcoming 2.0
> spec. :)
> Managing Director - Owner: www.intevation.net (Free Software
> Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-
> Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
> Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
More information about the format