Next Release

[Thomas Spuhler]

On Monday, September 07, 2015 07:24:53 AM Timotheus Pokorra wrote:
> >> I'm just wondering when the next Kolab release is due, as I am migrating
> >> our Mail server to new hardware, and would like to upgrade from Kolab
> >> 3.2 at the same time.
> > 
> > I would also be interested in this. Couldn't find any sort of roadmap
> > other
> > for Kolab 3.0 which is a bit old.
> 
> There is this tracker issue for Kolab 3.5:
> https://issues.kolab.org/show_bug.cgi?id=4563
> but I think it is more a wish list rather than a roadmap.
> 
> We talked about it on IRC. Jeroen is very busy with the infrastructure
> of the Kolab and KolabNow servers at the moment.
> 
> I guess since it is the community version, the community (that means
> us) need to help more with the release so that it can happen.
We do but it's kind of difficult. It would help a lot if at least the packages 
provided by kolabsystems would use the same versioning as Kolab, such a 
pykolab-3.5, libkolab-3.5, ect

> 
> Things still to figure out:
> * dependancy on composer: causes packages not to build for OpenSUSE.
> Any volunteers? I think I fixed it for Debian.
composer requires a few php-composer deps to build. Fedora has started to 
package them.

> * creating a 3.5 branch on OBS, and moving released packages there. We
> cannot just take Kolab Development because it is now updated directly
> from git master, not only for release tags. This is something only
> Jeroen can do?
> * Debian apache problems:
> https://issues.kolab.org/show_bug.cgi?id=2050 This happens for me now
> even during installation, so my automatic tests of Kolab Development
> hang and don't finish.

This isn't a problem with Mageia as far as I know.

But we haven't packaged Cyrus IMAP 2.5.x nor has Fedora as far as I can see.
This will be a major task

roundcubemail-plugins-kolab
This requires roundcube_version 1.2
I cannot find a roundcube_version 1.2. This involves 
libkolab doesn't currently build and I haven't gotten any reply on my inquiry 
on the ML

> * regarding https://issues.kolab.org/show_bug.cgi?id=4565: Supported
> Upgrades: Dirk was working on that, but I did not see the results yet.
> We have started the documentation but not finished:
> https://docs.kolab.org/upgrade-guide/kolab-3.5.html
> * release notes, etc
> 
> I am continually running basic tests on CentOS7 with Kolab
> Development, and they currently succeed if there is no LXC problem on
> the build host...
> https://lbs.solidcharity.com/logs/tbits.net/kolab-test/kolab-test/Developmen
> t/centos/7/amd64/24 Again, the 3.5 release will be different from Kolab
> Development.
> 
> I am CCing the devel list, perhaps we should continue discussing the
> technical side of the release there?
> 
> All the best,
>   Timotheus
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users

-- 
Best regards
Thomas Spuhler

All of my e-mails have a valid digital signature
ID 60114E63
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/users/attachments/20150908/a9b2fcce/attachment.sig>