New Horde web client finished

Gunnar Wrobel wrobel at pardus.de
Thu May 31 17:05:40 CEST 2007


ITSEF Admin <itsef-admin at itsef.com> writes:

> On Wednesday 30 May 2007 14:24, Gunnar Wrobel wrote:
>> As most of you know Horde has been an incomplete Kolab2 client for
>> quite a while now. The development to convert the web client into a
>> fully compatible Kolab2 client has been restarted last year and is
>> about to reach its final stage.
> [...]
>
> This is great news - thanks to everybody involved!
>
>
> [...]
>> In the meantime we encourage all people that do not run a production
>> server and that are interested in hosting a Horde web client to join
>> the bug hunting phase.
> [...]
>
> Well, as the only machine I can use for testing *is* a production server, I 
> have a few questions...
>
> - I have a few users who are eagerly awaiting a fully operable web client
>   and would most likely be willing to take the risk and help debugging.
>   Is there any chance that using Horde could screw things up for *other*
>   users? From what I understand it *shouldn't*, but what do I know... :-}
>
> - Currently, we use Squirrelmail for users who need to have access from the   
>   outside - is it possible to use Horde in parallel?
>

The last release for the Kolab-2.1_RC1 was definitely more problematic
in terms of "could damage you server". The last release had a patched
kolabd and kolab-webadmin package. The new release only has a newer
CVS version of the kolab-webadmin package. This makes it unlikely that
you damage any essential parts of your server. Once the next Kolab
version has been released, there will be no patched packages necessary
anymore. At that point the horde packages will be a simple add-on and
installing them means no risk (installing, not using!).

Now what could happen to the data of a user using the Horde web
client? I can give you no guarantees. While we stated that the web
client is finished this is only true with regard to the major
structural changes that were necessary. There will still be bugs that
will cause trouble when using Horde with Kolab. Since I currently
don't know most of these bugs :) I don't know if your users could
loose data when using Horde.

The current problem is also that we are using CVS snapshots
(http://ftp.horde.org/pub/snaps/). While this is a drastic improvement
to the prepatched p at rdus packages I used before it is not the same as
using stable, released packages. New packages will still be released
like every other week or so and I won't be able to test all Haorde
functionality for such a release.

I hope this helps in judging the potential problems of the current
packages. For production server I'd wait at least until the next Kolab
version has been released. And if you want to provide your users with
something reliable you should wait until Horde-3.2 has been
released. And no, this is not in a far and distant future :)
... http://wiki.horde.org/ShowStoppersThreeTwo

Cheers,

Gunnar


-- 
____ http://www.pardus.de _________________ http://gunnarwrobel.de _

    >> Mail at ease - Rent a kolab groupware server at p at rdus <<

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




More information about the users mailing list