update from kolab 3.1 to 3.3
Torsten Grote
torsten at kolab.org
Thu Sep 18 10:43:37 CEST 2014
On Thursday 18 September 2014 10:16:53 Toke Høiland-Jørgensen wrote:
> Would it be possible to have an 'upgrade' task to the setup-kolab that
> knew which db schema upgrades to apply (not asking you specifically,
> more of a general feature request)? :)
IMHO this should be done on package upgrades.
Our packages are all built publicly in OBS. So please have a look at them and
try to find if there is some upgrade routine in post-install missing
somewhere.
Kind Regards,
Torsten
--
Torsten Grote
Kolab.org Community Manager
e: torsten at kolab.org
w: https://Kolab.org
pgp: 0x2175A534A4F2EFA3
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/users/attachments/20140918/353c33a4/attachment.sig>
More information about the users
mailing list