On Wed, 17 Nov 2010, Jeroen van Meeuwen (Kolab Systems) wrote: > On Wednesday, November 17, 2010 11:29:21 am Ondřej Surý wrote: > > I am still busy as always, but I am very close for a need for newer > > cyrus for our systems, so I might put some effort into it. > > > > I propose we just skip 2.3 and go directly for 2.4 for squeeze+1. > > > > FWIW, I second the motion.
I agree with that (although I have now 2.3 in production). But we need to forward-port the patches (should be much easier now). In fact, for 2.4, we can even try the "upstream first" approach, since it sees a lot of code churn and timely new releases right now... BUT: upstream has not settled down on a workflow that allows for easy bug fixing patch flux that can be released with little notice when a very nasty bug gets fixed yet, so we might have to use a LOT of discretion before releasing a new upstream. But it looks like they have felt the need for that kind of workflow now, due to some nasty crap in 2.4.2/2.4.3 that wanted a quick fix+release, but there was unfinished work in the tree getting in the way. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh _______________________________________________ Pkg-Cyrus-imapd-Debian-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-cyrus-imapd-debian-devel
