[Kolab-devel] Horde webmail patch management for the Kolab web client

[Gunnar Wrobel]

Quoting Bernhard Reiter <bernhard at intevation.de>:

> On Sonntag, 11. Januar 2009, Gunnar Wrobel wrote:
>> The reason why Mathieu asked about this is because he considers the  
>>  big monolithic patch in Kolab CVS problematic to track.
>>
>> He is certainly right about that and I'm not 100% certain I chose  
>> the  right solution here.
>>
>> We originally had less than ten Kolab specific patches which I kept  
>> in  Kolab CVS. But I still had a lot of ongoing development within  
>> the  Kolab libraries after the horde-webmail-1.2.0 release. So I'm   
>> currently at more than 50 patches (most of them are already  
>> integrated  in Horde CVS though). And at some point I considered  
>> the monolithic  patch a better alternative for most users. You  
>> download  horde-webmail-1.2.0 to your machine, unpack it, download  
>> a single big  patch, apply it and you are done.
>>
>> I still believe this is the best way to go. But on the other hand  
>> the  way from the mercurial repository linked above to the final  
>> patch may  be somewhat obscure. Do people have better ideas? Or  
>> should I just  document it better in the wiki? Hoping for comments ;)
>
> This is a good question.
> Mathieu and other _could_ track changes to the big patch, which hopefully are
> not that large to stabilitze is.

The patch is mainly that large because a lot of relevant development  
in the Kolab modules happened only after the horde release we are  
currently using in the server.

> Single patch files seems to be be nicer if there is the change that more and
> more patches are getting upstream.

Most of these are actually already upstream. I'll have to see if we  
can switch over to a newer release version soon (meaning "before 2.2.1  
release"). I don't know if that will be possible though.

> I have a slight tendency towards
> smaller patch files, each patch addressing something which is a unit somehow.

I think I will add my patch queue to Kolab CVS soon anyhow. We use  
Horde 3 for the Kolab server and will continue to do so during the  
next two or three years. But I'm now starting preparations on  
switching to Horde 4. So Horde 3 is moving to maintenance rather than  
being in active development. So the patches are not that variable  
anymore.

>
> However the question can only be answered if we write up all pros and cons
> and consider them. (A wiki page is probably best for this.)

I hope I'll be able to work on the consolidation of the patch queue  
soon and maybe things are clearer afterwards. Maybe a wiki page won't  
be necessary then. On the other hand there will be development on  
Horde 4 and that in turn might warrant another page :) Lets see.

Cheers,

Gunnar

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



-- 
______ 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/20090122/8de123b9/attachment.sig>