[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kolab-format
Subject:    Re: 2.0rc7 -> 2.0 in two weeks
From:       Bernhard Reiter <bernhard () intevation ! de>
Date:       2008-04-30 14:24:18
Message-ID: 200804301624.27805.bernhard () intevation ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


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 this "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).

events:
s/<event version="1.0" >/<event version="2.0" >
contacts:
s/<contact version=1.0" >/<contact version="2.0">

the only problem was there with Toltec which did not display the objects.
Joon, can you confirm?

If so, this would be an argument for keeping "1.0" in the upcoming 2.0 
spec. :)

Best,
Bernhard
-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

[Attachment #5 (application/pgp-signature)]

_______________________________________________
Kolab-format mailing list
Kolab-format@kolab.org
https://kolab.org/mailman/listinfo/kolab-format


[prev in list] [next in list] [prev in thread] [next in thread]