[Kolab-devel] Freeze going for server 2.1.0beta

[Peter Marinov]

No problems with  OpenPKG 2.5.

Actualy I did not find any difference. Indeed, true multidomain support will
be great !



My versions:
Suse 9.2 
Kolab2 
2.0.1-security-update-20051014Kolab2 Groupware 
Server Component Versions
perl-kolab-5.8.7-2.0_20050912
kolabd-1.9.4-20050913
kolab-resource-handlers-0.3.9-20050912
kolab-webadmin-0.4.0-20050831
Kolab2 Patched OpenPKG Package Versions
amavisd-2.3.1-2.4.0
apache-1.3.33-2.4.1_kolab
imapd-2.2.12-2.4.0_kolab2
postfix-2.2.3-2.4.1_kolab
OpenPKG Version
openpkg-2.5.0-2.5.0


Regards,
Peter




-----Original Message-----
From: kolab-devel-bounces at kolab.org [mailto:kolab-devel-bounces at kolab.org]
On Behalf Of Bernhard Reiter
Sent: Tuesday, November 22, 2005 12:14 PM
To: kolab-devel at kolab.org
Subject: [Kolab-devel] Freeze going for server 2.1.0beta

Hi everybody,

as you know Server 2.1 is really due.

Our initial plan for getting is out did not fully worked out, because
a) we had to spend more work on security updates
b) Key developers Steffen and Bernhard H. were not as available as wished
c) We found more bugs that had to be fixed in 2.0.x, too.
d) The wonderful work of Richard Bos and Markus Hüwe help to 
    cleanup the implementation and make it even more modular

For quite a few users, a server is needed that has the minimal
multi-email-user capabilities of 2.1 and the stability of 2.0.x.
So our idea is to get 2.1 into that state soon.
This also means we will not fix all bugs for it, nor move to OpenPKG 2.5.
Basically we are in a freeze to get Kolab Server 2.1beta out of the door.
Our plan is to do this within the next 7 days.
Bernhard H. is working on it.

This means: Critical bug fixes only. 
                    Testing of new features and fixes that are already in
		    and possibly fixes for them.

Do we need a development branch for this?
I am unsure about it. Actually I do not want to spread out the development
of the server too much as a high priority is stability. Kolab already works
in many environments and we need to keep it this way, offering well testing
upgrade paths.
So my suggestion is to make the development branch, if server 2.1 can fully
replace the 2.0.x servers.

About OpenPKG 2.5: We believe this is a 4 to 5 days worth of work, but this
is a place non-key developers can help:
Try OpenPKG 2.5 on your platform, especially the packages that Kolab Server
will use. Next try to integrate the patches and then build Kolab Server
packages.

As always: report on this list!

Bernhard
 

_______________________________________________
Kolab-devel mailing list
Kolab-devel at kolab.org
https://kolab.org/mailman/listinfo/kolab-devel