[Xapian-discuss] Xapian 1.1.0 development snapshot released

[Olly Betts]

I've uploaded Xapian 1.1.1.  Please note that 1.1.x releases are
development releases - if you want ABI stability and minimal risk of
accidental breakage, please stick with 1.0.x for the time being.

The 1.1.x development series will lead to a stable 1.2.x release series.
It's hard to guess at a timescale right now, but it will be months
rather than weeks or years.

If you make binary packages of this release, please make sure that
they are very clearly labelled as not being a stable version, and if
possible ensure that they can be installed in parallel with the stable
version (the default paths and program suffix are set to help make this
easier).  I would probably recommend not rushing to package this right
away.  I'm intending to wait for things to settle down a bit before
building Debian or Ubuntu packages.

I've not yet put together release notes or a download page yet, but
you can read the full lists of user-visible changes here:

  http://svn.xapian.org/*checkout*/tags/1.1.1/xapian-core/NEWS

  http://svn.xapian.org/*checkout*/tags/1.1.1/xapian-applications/omega/NEWS

  http://svn.xapian.org/*checkout*/tags/1.1.1/xapian-bindings/NEWS

  http://svn.xapian.org/*checkout*/tags/1.1.1/search-xapian/Changes

Note in particular that 1.1.1 includes all relevant changes which were in
1.0.13.

And the source tarballs are available from here:

http://oligarchy.co.uk/xapian/1.1.1/

Here are the SHA1 checksums of the released files:

442a526dd9368c1028b581e62d47719cdf781e1b  Search-Xapian-1.1.1.0.tar.gz
0ca15f285ad5b639b23aecf77811ab690ae2cad5  xapian-bindings-1.1.1.tar.gz
66e09d737137e2cd153840fedfaa7caaef28bcc7  xapian-core-1.1.1.tar.gz
aeb3daaa411dc910d8cffc1321a5861db3af3d8c  xapian-omega-1.1.1.tar.gz

And the SHA256 checksums:

b3389b83abb0afec478c603c1540fc05a634171e665a7d38248bc4f5296afb31  Search-Xapian-1.1.1.0.tar.gz
7da5dec23c096c9832ca0d5540707098099f4f2c2ca320bd6bccefa947ab6693  xapian-bindings-1.1.1.tar.gz
2cc1e05baa65fa675d2745fdf90b4a99cdd663b249ebd67ba280df2daaf8943f  xapian-core-1.1.1.tar.gz
8308efd9d6090860ba99d89338e5c4c69ef0715c3e9aab13ca8da80dc957217b  xapian-omega-1.1.1.tar.gz

This announcement is GPG-signed, 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).

I've generated a new GPG key (which doesn't use an SHA1 hash) which I'll
be using to sign future releases.  This new key is signed by my old key
and has two other signatures so far.  

The new key has fingerprint:

08E2 400F F7FE 8FED E3AC  B528 1814 7B07 3BAD 2B07

I was intending to sign releases with both keys for a while, but this
feature doesn't seem to work in a useful way for this purpose - GPG at
least only checks the first of multiple signatures (and issues a warning
to this effect).  So I'll sign this message with the old key, and switch
to the new key for 1.1.2 - you can use the fingerprint above to establish
continuity of signing if you don't have a trust chain to my key.

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

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/20090610/9837c3de/attachment.pgp