[Kolab-devel] Server 2.2.0b2 release doc remarks

[Bernhard Reiter]

On Thursday 25 October 2007 18:25, Thomas Arendsen Hein wrote:
> > release-notes.txt release-notes.txt,v 1.160 2007/10/19
> > * Should be longer and contain the previous release notes as well.
>
> I already removed the history before 2.1.0, but I really want to
> have the full history since creation of the 2.2 branch.

I think we should keep the full history since 2.0
similiar to what postfix does. Usually grepping in there is really helpful.
Or we include the direct link to it.

> > * Should mention that Horde might create load on the server
> >   which makes it recommendable to use a second server for this.
>
> In this case there should be an install option for only Horde
> without the other Kolab server components, which is currently not
> possible out of the box.

We need this scenario, yes, but the hint should be there nontheless.
Also there is no problem with installing the full package on two machines
and only use Horde from one (if we had the config options for this.)


> Can anyone provide one which isn't too long?
> /media/cdrom/kolab-server/install-kolab.sh -H -F -i
> /media/cdrom/kolab-server

  /cdrom/src/install-kolab.sh -H -F -i /cdrom/src

or /path/to/install-kolab.sh -H -F -i /cdrom/kolab-server-src

> > * probably should be 2.2.0-beta2 instead of
> >                 Kolab version (KOLAB_VERSION):      2.2-beta2
>
> Of course the release will be called 2.2.0.
>
> To make OpenPKG's RPM happy we had the possibility to use:
> 2.1.99-beta2
> 2.2-beta2
> 2.2.0-beta2 with using the Epoch statement
>
> PHP/PEAR added further restrictions to what version numbering
> schemes we can use.
>
> There is a bit of discussion about that on this list.

I know, I saw it, but I probably missed the detail for why we leave out
the ".0". I guess we really should document the result of this discussion
in the wiki somewhere.

> > General remarks:
> > * We should include hints for upgrading older servers.
> >   Especially from 2.0.4 to 2.2.0 will be interesting.
>
> Of course, as I wrote in the README:
> | Instructions for upgrading from Kolab server 2.0 or 2.1 will be added
> | in a future version of this document.

I know, my point is: There should be instructions to directly jump
from 2.0.4 to 2.2.0. And from 2.1.0 to 2.2.0.
In the meantime we could point to a wiki page with first hints.

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20071025/97c07411/attachment.sig>