[Pkg-owncloud-maintainers] Fwd: [Owncloud] 4.0.1
Diederik de Haas
didi.debian at cknow.org
Sat May 26 13:36:39 UTC 2012
Paul van Tilburg <paulvt at debian.org> wrote:
>-------- Originalnachricht --------
>Betreff: [Owncloud] 4.0.1
>Von: Frank Karlitschek <frank at owncloud.org>
>An: "owncloud at kde.org Mailinglist" <owncloud at kde.org>
>we want to release a 4.0.1 bugfix release as soon as possible to
>all the issues of the ownCloud 4 release.
>The plan is to release 4.0.1 the coming friday and a 4.0.2 one or two
>So please backport your fixes to the stable 4 branch for the release.
>I think it it important that we stabilize the ownCloud 4 code base as
>much as possible now.
>Owncloud mailing list
>Owncloud at kde.org
>----- End forwarded message -----
>P.S. This is a forward of a forward from Thomas.
>Using the Power of Debian GNU/Linux | E-mail: paulvt at debian.org
>Jabber/GTalk: paul at luon.net | GnuPG key ID: 0x50064181
>Pkg-owncloud-maintainers mailing list
>Pkg-owncloud-maintainers at lists.alioth.debian.org
I was quite pleased when I saw the msg :-)
What are the possibilities/restrictions when it comes to integrating those point releases into the Debian pkgs for wheezy?
I've read that the freeze is planned for june, but I haven't found which date it will be. June 1st or june 30th therfor seems to matter a lot wrt to this.
I guess we can integrate the 4.0.1 release, but the 4.0.2 could be tricky.
Say that if the freeze happens before 4.0.2 is released, does that mean we can only cherry-pick the (upstream) commits for fixes for which a RC bug is present in debian's BTS? What other options are there? And how can we utilise them to the fullest?
PS: one of you happen to have a hand in this 'sudden' announcement of the point releases? ;-)
More information about the Pkg-owncloud-maintainers