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

[Gunnar Wrobel]

Quoting Richard Bos <ml at radoeka.nl>:

> 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 believe Bernhard has been referring to the functional aspects of the  
Kolab Server and we do indeed hope that this will be very smooth  
transition on the OpenPKG version.

> 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.

If you had a clean perl rpm spec for perl-kolab all you need to do is  
to remove the kolabconf package.

I am using the language specific packaging methods where ever I can.  
This means packaging for you platform should actually get easier not  
more complex.

Cheers,

Gunnar

>
> 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.
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel



-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
--------------------------------------------------------------------
    >> Mail at ease - Rent a kolab groupware server at p at rdus <<
--------------------------------------------------------------------


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
URL: <http://lists.kolab.org/pipermail/devel/attachments/20081027/7e3b053a/attachment.sig>