[Xapian-discuss] Xapian 1.0.13 released

[Olly Betts]

I've uploaded Xapian 1.0.13 (including Search::Xapian 1.0.13.0), which
as usual you can download from:

http://xapian.org/download

Here are the SHA1 checksums of the released files:

d90e7ea2ba000bf28947e5da820455594461637c  Search-Xapian-1.0.13.0.tar.gz
2d8bd20b5dd1fc0554a1ac4be047e9b35310e000  xapian-bindings-1.0.13.tar.gz
c08eca16b8816e244cd30c35d2fe53d49f78cd77  xapian-core-1.0.13.tar.gz
9fcb1dd92c7d08e9ce3bbeba22086674dee272df  xapian-omega-1.0.13.tar.gz

And for those worried about SHA1's strength, here are SHA256 checksums:

f6d2d86df70e97e0339974b6d7aaf0f2490550982fc903ce21e7ca68fa365021  Search-Xapian-1.0.13.0.tar.gz
bd57ab5db7dc4e33cbc8c25255823ec27f5a8812a62210f5711253db8e537300  xapian-bindings-1.0.13.tar.gz
a474be06657bd83200231d938d48d4d2a83cff0252c618421f835604c5548dce  xapian-core-1.0.13.tar.gz
f4300215b8ea57accee670ccc8ae2f840319966d21c8b725f2998d5ad4619728  xapian-omega-1.0.13.tar.gz

I have signed this announcement with my GPG key, so if you can establish a
trust chain to my key, and you verify the checksums, you can be confident that
the tarballs you downloaded are the same as those I uploaded (even if you get
them from a mirror).  If you can't establish a trust chain, you can still
verify the checksums (and also see that the same key is being used to sign
each release announcement).

I'm intending to generate a new key in the near future, which I'll sign
with my current key and try to get a few other signatures on.  I'll then
sign release announcements with both keys for a while.

This release fixes a few bugs, adds a couple of new little features, and
makes several performance improvements to the matcher.

Notable changes in this release:

* A long standing problem with deadlocks when trying to use the Python bindings
  with mod_python has been worked around (the problem is due to bugs in
  mod_python which are apparently unlikely to ever be fixed).

* scriptindex has a new "valuenumeric" action for indexing values suitable for
  numeric sorting.

* Perl has a new set of example programs.

* The Perl bindings have a new Search::Xapian::MSet::matches() method which
  ties the MSet to a Perl array (like Search::Xapian::Enquire::matches(), but
  this method makes more sense on MSet than Enquire.  However, I've just
  spotted I failed to apply a patch where I changed my mind and called this
  "items()" (for consistency with a patch on trunk to add support for tying
  ESet objects to arrays - also Python has 'MSet.items' and 'ESet.items'
  properties, and while consistency between the Perl and Python bindings is not
  so important for most users, it's not a bad thing).  So I guess consider the
  new method deprecated already - I'll see if I can find time to put 1.0.13.1
  out soon.

For a more detailed overview see:

http://trac.xapian.org/wiki/ReleaseOverview/1.0.13

The full lists of user-visible changes are linked to from there, and
from the "[news]" links on the download page.

As always, if you encounter problems, please report them here, or to
the bug-tracker: http://xapian.org/bugs

A new development release (1.1.1) should be out later this week too.

Cheers,
    Olly
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
Url : http://lists.xapian.org/pipermail/xapian-discuss/attachments/20090525/30d64777/attachment.pgp