[Kolab-devel] Kolab Server 2.2-beta1 based on OpenPKG-CURRENT, RFC for CVS

[Gunnar Wrobel]

Thomas Arendsen Hein <thomas at intevation.de> writes:

> Hi!
>
> Source and Debian etch ix86 binary installer downloadable from:
> http://ftp.belnet.be/packages/kolab/server/beta/kolab-server-2.2-beta-1/
> ftp://ftp.belnet.be/packages/kolab/server/beta/kolab-server-2.2-beta-1/
> http://www.erfrakon.de/mirrors/ftp.kolab.org/server/beta/kolab-server-2.2-beta-1/
> as soon as mirroring has catched up.
>
> The install instructions are currently only in German, here is a
> very short version:
>
> 1. copy source or ix86-debian4.0 files to a directory writable for root
> 2. ./install-kolab.sh openpkg-*.sh
> 3. /kolab/etc/kolab/kolab_bootstrap -b
>
> Compiling from source took 3 hours on a test system (P4 2.8GHz),
> installing the binaries 3 minutes on the same system.
>
>
> All this is not in CVS yet, but patches are available in addition to
> the sources directory. Here is my RFC how to add this to CVS:
>
> - create a "kolab_2_1_branch" branch for the server directory,
>   currently most things could go in there as kolab 2.1.1 should
>   contain some new features, e.g. better Horde support and
>   kolab/issue1340 (restrict users to sending mail only to internal recipients)
>
> - everything that goes into this branch should regularly be merged
>   into HEAD:
>
>   In HEAD branch:
>     cvs update -A  # just to be sure
>     cvs update -kk -j merged_2_1_branch -j kolab_2_1_branch
>
>   In 2.1 branch:
>     cvs update -r kolab_2_1_branch  # just to be sure
>     cvs tag merged_2_1_branch
>
> - If things happen in kolab_2_1_branch that shouldn't go into HEAD,
>   e.g. bumping version numbers for releases, the merged_2_1_branch
>   tag can simply be moved forward.
>
> - When development for 2.1 branch settles down, primary development
>   will move to HEAD and merging is no longer performed.
>
> Any comments or suggestions about this?

Sounds fine to me.

> Additionally I was thinking about moving the templates into a
> separate package, so different distributions can provide their own
> version, or we can simply release updated templates when non-kolab
> components are upgraded without providing a new kolabd package.

+1

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