[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [Libevent-users] ANN: Libevent 2.0.9-rc is released



And I have a Windows and Solaris compile patch for you too :-)

My bad - I'm behind in getting it to you.


On Nov 30, 2010, at 7:41 AM, Kelly Brock wrote:

> Great news but the iocp fix needs a minor fix:
> 
> Line 618 & 619 need to be modified as follows:
> 		setsockopt(sock, SOL_SOCKET, SO_UPDATE_ACCEPT_CONTEXT,
> 		    (char *)&as->lev->fd, sizeof(&as->lev->fd));
> 
> This is due to the line just obove setting as->s to invalid.
> 
> KB
> 
>> -----Original Message-----
>> From: owner-libevent-users@xxxxxxxxxxxxx [mailto:owner-libevent-
>> users@xxxxxxxxxxxxx] On Behalf Of Nick Mathewson
>> Sent: Tuesday, November 30, 2010 1:12 AM
>> To: libevent-users@xxxxxxxxxxxxx
>> Subject: [Libevent-users] ANN: Libevent 2.0.9-rc is released
>> 
>> Libevent 2.0.9-rc is released!
>> 
>> Thanks to many people's hard work, Libevent 2.0 has now had its fourth
>> release candidate.  You can download it from the Sourceforge site at:
>> 
>> https://sourceforge.net/projects/levent/files/libevent/libevent-
>> 2.0/libevent-2.0.9-rc.tar.gz/download
>> 
>> There's also a pgp signature of it (by me) there, at:
>> 
>> https://sourceforge.net/projects/levent/files/libevent/libevent-
>> 2.0/libevent-2.0.9-rc.tar.gz.asc/download
>> 
>> Don't forget to validate the signature.   The complete list of changes
>> is available in the ChangeLog file, included with the distribution.
>> 
>> Niels will upload this to monkey.org when he can; he's been super-busy
>> with his work lately, which is why I've been doing the "lead
>> developer" stuff these days.
>> 
>> *** What's new in Libevent 2.0.9-rc
>> 
>> Thanks to everybody who reported and fixed bugs in Libevent 2.0.8-rc,
>> Libevent 2.0.9-rc should be much more stable and a little more
>> portable, especially if you're using epoll, OpenSSL bufferevents,
>> filtering bufferevents, IRIX, 64-bit Windows, filtering bufferevents,
>> evdns*cancel(), or evhttp.  Especially evhttp.
>> 
>> This release was going to be the "2.0.9-stable", but instead it's
>> still a release candidate.  That's because of the epoll+dup bugs that
>> forced us to roll back the default behavior of the epoll backend to
>> not use the faster changelist-based logic.
>> 
>> For a complete list of changes, just see the ChangeLog included with
>> the source distribution.  HTTP-related changes are split into their
>> own sections.
>> 
>> *** Fun facts about Libevent 2.0.9-rc:
>> 
>> This release changes a bunch of lines.  Not to fear, though: they're
>> mostly in the unit tests, the samples directory, and HTTP-related
>> stuff.
>> 
>> 2.0.9-rc 63 files changed, 4269 insertions(+), 936 deletions(-)
>> 2.0.8-rc: 54 files changed, 981 insertions(+), 343 deletions(-)
>> 2.0.7-rc: 61 files changed, 2459 insertions(+), 685 deletions(-)
>> 2.0.6-rc: 104 files changed, 1749 insertions(+), 1192 deletions(-)
>> 2.0.5-beta: 122 files changed, 3283 insertions(+), 1194 deletions(-)
>> 2.0.4-alpha: 122 files changed, 8112 insertions(+), 4190 deletions(-)
>> 2.0.3-alpha: 98 files changed, 10131 insertions(+), 2213 deletions(-)
>> 2.0.2-alpha: 90 files changed, 5677 insertions(+), 1619 deletions(-)
>> 2.0.1-alpha: 113 files changed, 23909 insertions(+), 7670 deletions(-)
>> 
>> Unit test coverage (by line) is up to 80.04% on my Linux box--finally,
>> we're over 80% coverage again!  Branch coverage is at 71.01% according
>> to gcov, up from 69.92%.  More tests are still needed, particularly
>> for these files:
>>   WORST LINE COVERAGE -- bufferevent_ratelim.c, evutil.c,
>>     bufferevent_openssl.c
>>   WORST BRANCH COVERAGE -- evutil_rand.c, evdns.c, bufferevent_ratelim.c
>>   MOST UNTESTED LINES -- evnds.c, http.c, evutil.c, buffer.c, event.c
>>   MOST UNTESTED BRANCHES -- evdns.c, buffer.c, http.c, event.c
>> 
>> *** Status: Libevent 2.0.x-rc and beyond.
>> 
>> Libevent 2.0 is *still* in feature-freeze (we won't add any more
>> features to it), hack-freeze (no clever backend rewrites,
>> refactorings, or major performance hacks), and API freeze (all code
>> written to work with the documented APIs of Libevent 2.0.5-beta should
>> continue to work with future versions of Libevent).  We might change
>> our minds about any of the above if there turn out to be exceptionally
>> good reasons to do so; this is an aspiration, not a promise. ;)
>> 
>> Please upload bug reports and patches to the sourceforge site at
>> https://sourceforge.net/projects/levent/ .  Feature requests and
>> non-bugfix enhancements will be acknowledged but politely deferred
>> till we fork Libevent 2.0 into a stable maintenance branch and start
>> development on 2.1.  I'm hoping to do that around 2.0.10-stable, which
>> I hope to have out before the new year.
>> 
>> We're almost out of known bugs with the 2.0.x series.  If you know
>> about a bug that 2.0.9-rc does not fix, please have a quick look at
>> the bug tracker to make sure that there is an entry there.  If there
>> is not, then please don't assume that we remember it, even if you
>> mentioned it here, or emailed me personally, or such.
>> 
>> *** Acknowledgements
>> 
>> Many thanks to everybody who contributed code, suggestions, or bug
>> reports to this release, including but absolutely not limited to
>> Christopher Davis, Bas Verhoeven, Dagobert Michelsen, Denis Bilenko,
>> Dimitre Piskyulev, Felix Nawothnig, Gilad Benjamini, Ivan Andropov,
>> Joachim Bauch, Jason Toffaletti, Julien Blache, Kelly Brock, Kevin
>> Bowling, Linus Nordberg, Mark Ellzey, Nicholas Marriott, Pavel Plesov,
>> Sebastian Hahn, Trond Norbye, and Yan Lin.
>> 
>> eventfully yrs,
>> --
>> Nick Mathewson
>> ***********************************************************************
>> To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
>> unsubscribe libevent-users    in the body.
> 
> ***********************************************************************
> To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
> unsubscribe libevent-users    in the body.

***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users    in the body.