Time for 2.3.13?
wes at umich.edu
Wed Sep 10 09:45:07 EDT 2008
I see 12 items in the bugzilla (one of which is the skiplist foreach
bug) which I think can be closed. So, yes, I think we should get
these various fixes committed and begin rolling 2.3.13. Can you make
sure bugzilla has the versions of these various patches that you
think should be applied to HEAD?
On 10 Sep 2008, at 02:43, Bron Gondwana wrote:
> I just noticed that 2.3.12 was released back in April, and
> there are a few fixes changes kicking around. I've just
> compared CVS HEAD to 2.3.12 using trusty old 'diff' and
> it looks like the big changes are:
> * sql database support
> * "can not" => "cannot"
> * capabilities tidy up
> * cyr_virusscan
> I'd also like to push the following patches upstream:
> * http://cyrus.brong.fastmail.fm/patches/cyrus-skiplist-locking-
> - we've discussed this one in detail in other threads,
> and people who've tested it report it working well.
> * http://cyrus.brong.fastmail.fm/patches/cyrus-skiplist-
> - pretty trivial fix to make consistency checks safe
> against failures. Probably pointless, but it makes
> the code nicer.
> * http://cyrus.brong.fastmail.fm/patches/cyrus-always-
> - absolutely trivial patch in the style of other fixes.
> Put an "unlink" call before an open call on a file that's
> not supposed to be there in the stage area. Just in case[tm].
> * http://cyrus.brong.fastmail.fm/patches/cyrus-longwords-2.3.4.diff
> - seriously, who is doing email with a 10Mb memory machine these
> days? We've had a query just recently on the mailing list where
> a site hit line length issues. Let the VM handle it.
> I don't think I'd push nested transactions upstream at this stage -
> it works fine for me, but it's pretty experimental still! I'm more
> interested in having a robust skiplist implementation that handles
> the 'foreach used first' bug. Then if anyone asks about skiplist
> issues I can just say "use 2.3.13" rather than "use 2.3.12 plus
> these patches" :)
More information about the Cyrus-devel