I'm happy to be able to announce that Xapian 1.3.4 is now available.
Please note that 1.3.x releases are development releases - they are made
to encourage earlier and wider use and testing of new and changed code.
Our record with 1.1.x was very good - all the bugs I am aware of were
either in new features, or were also present in the corresponding 1.0.x
release. But if you main concern is minimising risk of accidental
breakage, sticking with 1.2.x would be prudent, at least for deployment.
The 1.3.x development series will lead to a stable 1.4.x release series.
We don't yet have a date set for when that will happen, but we're
certainly
closing in on 1.4.0.
If you make packages of this release, please make sure that they are
very clearly labelled as not being a stable version, and 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). If they are
binary packages you should also be aware that 1.3.x comes with no
guarantee of ABI stability (code built against 1.3.3 will need
rebuilding for 1.3.4).
There's been exactly 6 months of development work since 1.3.3, so the lists
of changes are substantial and I won't try to summarise them here. You can
read the full lists of user-visible changes here:
http://xapian.org/docs/xapian-core-1.3.4/NEWS
http://xapian.org/docs/xapian-omega-1.3.4/NEWS
http://xapian.org/docs/xapian-bindings-1.3.4/NEWS
Note that 1.3.4 includes all relevant changes that were in 1.2.22.
As always, if you encounter problems, please report them here, or to
the bug-tracker: http://xapian.org/bugs
The source tarballs are available from here:
http://oligarchy.co.uk/xapian/1.3.4/
A big thankyou to the following people for helping to make this release
a reality: Richard Boulton, coventry, Philip Neustrom, James Aylett,
Will Greenberg, Emmanuel Engelhart, Dylan Griffith, Jorge C. Leit?o,
UsusDei, boomboo, Charles Atkinson, Brian Burton, Gaurav Arora, Marco
Hennigs, Thomas Viehmann, Pavel Strashkin, Mikkel Kamstrup Erlandsen,
Brandon Schaefer, Dagobert Michelsen, matf, Germ?n M. Bravo, Eric Lindblad,
Josh Elsasser, John Alveris, Andrew Chilton, lhz7370, Val Rosca, Andreas
Marienborg, and Andreas V?gele.
If I've missed anyone out, you can claim an extra big thankyou.
As always, if you encounter problems, please report them here, or to the
bug-tracker: http://xapian.org/bugs
Since 1.2.17, I'm providing detached GPG signatures for each of the
release tarballs (for each tarball, the signature is in a corresponding
file with ".asc" appended).
Here are the SHA1 checksums of the released files:
4e6a46b1898c91267d1319ff23ae860d7799b2a8 xapian-bindings-1.3.4.tar.xz
a51c75fa7fe55a57b92228e67e7213e9f1ebc7b9 xapian-core-1.3.4.tar.xz
5379eae77e47b645673a7795ba3bd35f86097a8e xapian-omega-1.3.4.tar.xz
And SHA256 checksums (more secure, but sha256sum is less widely
installed):
c2481c49007392ebe5f7a1bfbd88c528e329b74650a985dd3c7d3d6649d58498
xapian-bindings-1.3.4.tar.xz
0a49da54a1eecb43de657f6341fde386f4c6e6bd1d2d64f77212adfc44bf67d4
xapian-core-1.3.4.tar.xz
f6f31bd46194703adc317cfdbd62ce423fc2f9c96b7b1c9fb2a6bfa2f88779d7
xapian-omega-1.3.4.tar.xz
Cheers,
Olly
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL:
<http://lists.xapian.org/pipermail/xapian-discuss/attachments/20160101/9767708b/attachment.sig>
On Fri, 01 Jan 2016 at 18:19, Olly Betts wrote:>I'm happy to be able to announce that Xapian 1.3.4 is now available. > >Please note that 1.3.x releases are development releases - they are made >to encourage earlier and wider use and testing of new and changed code. > >Our record with 1.1.x was very good - all the bugs I am aware of were >either in new features, or were also present in the corresponding 1.0.x >release. But if you main concern is minimising risk of accidental >breakage, sticking with 1.2.x would be prudent, at least for deployment. > >The 1.3.x development series will lead to a stable 1.4.x release series. >We don't yet have a date set for when that will happen, but we're certainly >closing in on 1.4.0. > >If you make packages of this release, please make sure that they are >very clearly labelled as not being a stable version, and 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). If they are >binary packages you should also be aware that 1.3.x comes with no >guarantee of ABI stability (code built against 1.3.3 will need >rebuilding for 1.3.4). > >There's been exactly 6 months of development work since 1.3.3, so the lists >of changes are substantial and I won't try to summarise them here. You can >read the full lists of user-visible changes here:Hey Olly, I'm getting a 404 for these links.> http://xapian.org/docs/xapian-core-1.3.4/NEWS > http://xapian.org/docs/xapian-omega-1.3.4/NEWS > http://xapian.org/docs/xapian-bindings-1.3.4/NEWS>Note that 1.3.4 includes all relevant changes that were in 1.2.22. > >As always, if you encounter problems, please report them here, or to >the bug-tracker: http://xapian.org/bugs > >The source tarballs are available from here: > >http://oligarchy.co.uk/xapian/1.3.4/ > >A big thankyou to the following people for helping to make this release >a reality: Richard Boulton, coventry, Philip Neustrom, James Aylett, >Will Greenberg, Emmanuel Engelhart, Dylan Griffith, Jorge C. Leit?o, >UsusDei, boomboo, Charles Atkinson, Brian Burton, Gaurav Arora, Marco >Hennigs, Thomas Viehmann, Pavel Strashkin, Mikkel Kamstrup Erlandsen, >Brandon Schaefer, Dagobert Michelsen, matf, Germ?n M. Bravo, Eric Lindblad, >Josh Elsasser, John Alveris, Andrew Chilton, lhz7370, Val Rosca, Andreas >Marienborg, and Andreas V?gele. > >If I've missed anyone out, you can claim an extra big thankyou. > >As always, if you encounter problems, please report them here, or to the >bug-tracker: http://xapian.org/bugs > >Since 1.2.17, I'm providing detached GPG signatures for each of the >release tarballs (for each tarball, the signature is in a corresponding >file with ".asc" appended). > >Here are the SHA1 checksums of the released files: > >4e6a46b1898c91267d1319ff23ae860d7799b2a8 xapian-bindings-1.3.4.tar.xz >a51c75fa7fe55a57b92228e67e7213e9f1ebc7b9 xapian-core-1.3.4.tar.xz >5379eae77e47b645673a7795ba3bd35f86097a8e xapian-omega-1.3.4.tar.xz > >And SHA256 checksums (more secure, but sha256sum is less widely >installed): > >c2481c49007392ebe5f7a1bfbd88c528e329b74650a985dd3c7d3d6649d58498 xapian-bindings-1.3.4.tar.xz >0a49da54a1eecb43de657f6341fde386f4c6e6bd1d2d64f77212adfc44bf67d4 xapian-core-1.3.4.tar.xz >f6f31bd46194703adc317cfdbd62ce423fc2f9c96b7b1c9fb2a6bfa2f88779d7 xapian-omega-1.3.4.tar.xz > >Cheers, > Ollyrgh
On Fri, Jan 01, 2016 at 04:48:30PM +1100, Richard Heycock wrote:> I'm getting a 404 for these links. > > > > http://xapian.org/docs/xapian-core-1.3.4/NEWS > > http://xapian.org/docs/xapian-omega-1.3.4/NEWS > > http://xapian.org/docs/xapian-bindings-1.3.4/NEWSOops, sorry about that. Adding these files wasn't part of the scripted website update for a development snapshot (only for a stable release). I've just fixed that, and rerun the website update. So it's now fixed, and should just happen automatically in the future. Thanks for reporting. Cheers, Olly