[Kolab-devel] RFC next kolab server version 2.3 and 2.2.1?

[Richard Bos]

Bernard,

Op Tuesday 21 October 2008 11:49:05 schreef Bernhard Reiter:
> On Dienstag, 21. Oktober 2008, Gunnar Wrobel wrote:
> > > With a version of 2.2.1 people may blindly upgrade, assuming hardly any
> > > changes were made.
>
> On the roadmap are only minor changes from the users
> (aka Kolab Server Admin) perspective.
>
> > > With a 2.3 version number people will be more
> > > carefull. Looking it from a cvs point of view: 2.2.1 should be a branch
> > > from 2.2.0. 2.3 is further on, on the trunk.   The latter is what is
> > > happening with kolab.
> >
> > Yes, you convinced me, too.
> >
> > 2.3 would be better. Bernhard, Thomas?
>
> Ideally 2.2.1 would just go in very smoothly on an update
> and this is the version I hope we get which would also warrent that
> particular version number.

Forget the Ideally word in your sentence above.  The current situation is 
quite messy.  At the moment I can't do a testbuild for openSUSE at all 
because I have no idea what I need to package, as I have no idea what has 
been moved and to which module it has been moved.  That very much 
contradicts "go in very smoothly on an update" above.
I understood that with the current situation the kolabconf package has been 
integrated in the perl-kolab package.  This means that on package level a 
whole package is gone, and special rules have to be added the perl-kolab 
package to obsoletes the kolabconf package.  That is only one example, 
besides the many others I have given before.

Hence I believe that with the current state of affairs the roadmap has to be 
updated with a 2.3 version.  The 2.2.1 version can still be released (just 
check the 2.2.0 sources and apply the fixes for 2.2.1 and release), but the 
current code is not a minor upgrade.


-- 
Richard Bos
We are borrowing the world of our children,
It is not inherited from our parents.