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

[Bernhard Reiter]

On Donnerstag, 22. Januar 2009, Gunnar Wrobel wrote:
> 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.

This sounds strange somehow.
Maybe we need an enterprise branch for Horde (preferable in their SCM)
like we have with Kontact. The problem is that we only want a stable
Kolab Webclient, but in order to do so, we need to be able to develop
(conservatively) and somehow track the differences.

Maybe I need to read-up on Horde release tactic, is there a document about 
this that you can recommend?


-- 
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 206 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20090122/8cbfe1f6/attachment.sig>