[Libevent-users] ANN: Libevent 2.0.15-stable is released

[Nick Mathewson <nickm@xxxxxxxxxxxxx>]

Hello, all!

Announcing Libevent 2.0.15-stable
=================================

Libevent 2.0.15-stable is now tagged and released.  The package is
available from the *shiny new website* at http://libevent.org/ .

There are GPG signatures there too; you should probably verify them,
to make sure you get the software you think you are getting.

What's New in Libevent 2.0.15-stable
====================================

This release fixes a few DNS, evbuffer, and signal issues.  If
you're affected by one of these issues, then 2.0.15-stable should improve
matters for you.  It also fixes some annoying compiler warnings in
the unit tests from newer GCC versions.

Here's the ChangeLog for this release:

BUGFIXES (DNS):
 o DNS: add ttl for negative answers using RFC 2308 idea. (f72e8f6
Leonid Evdokimov)
 o Add DNS_ERR_NODATA error code to handle empty replies. (94fba5b
Leonid Evdokimov)

BUFGIXES (bufferevents and evbuffers):
 o Make evbuffer callbacks get the right n_added value after
evbuffer_add (1ef1f68 Alex)
 o Prefer mmap to sendfile unless a DRAINS_TO_FD flag is set. Allows
add_file to work with SSL. (0ba0af9)

BUGFIXES (event loop):
 o When a signal callback is activated to run multiple times, allow
event_base_loopbreak to work even before they all have run. (4e8eb6a)

DOCUMENTATION FIXES:
 o Fix docstring in dns.h (2b6eae5 Leonid Evdokimov)
 o refer to non-deprecated evdns functions in comments (ba5c27d Greg Hazel)

BUILD AND TESTING FIXES:
 o le-proxy and regress depend on openssl directly (9ae061a Sergey Avseyev)
 o Use _SOURCES, not _sources, in sample/Makefile.am (7f82382)
 o Fixed compiler warnings for unchecked read/write calls. (c3b62fd Mark Ellzey)
 o Make write-checking fixes use tt_fail_perror (2b76847)
 o Fix some "value never used" warnings with gcc 4.6.1 (39c0cf7)


Boring facts about Libevent 2.0.15-stable
=========================================

The diff between this release and the last is 665 lines long, which
makes it the shortest in the whole 2.0.x series, breaking the record
previously held by 2.0.14-stable.

Barring new big problems, I am going to start putting out 2.0
releases less frequently.  Previously, I've been going for "about a
month to 45 days".  Now I'll go with "about a month to 45 days if
there's a serious bug; about 60-90 days if nothing major has
changed."

I'm also hoping to get Libevent 2.1.1-alpha out in the next few
months.  The feature set will mostly be determined by the patches
people write.

Acknowledgments
===============

Thanks to everybody who helped with code, bug reports, and suggestions,
including but not limited to:

  Alex
  Sergey Avseyev
  Adrian Chadd
  Mark Ellzey
  Leonid Evdokimov
  Greg Hazel
  Abilio Marques
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users    in the body.