Libevent 2.1.6-beta was released in July this year. The current stable build (2.0.22) was released in Jan 2015, the same time as the previous beta.
Not using 2.1.x is affecting atleast
There are also compatibility issues with 2.0.22 and recent mingw-w64 gcc versions, see #8730
Optimistically tagged this as something for 0.14.0
Some further backstory here: libevent's release process is slow. Maintenance is in no means standing still, many improvements have been made in the 2009-now timeframe. However, these have not ended up in the stable versions (2.0.x). Even some bugfixes have not, I had to push to get a basic IPv6 http fix in at some point (which had been in 2.1.x for a long time).
Branch 2.1.x had been in alpha for years, and has entered beta 2015-01-05 with 2.1.5. Despite not officially being called stable yet it seems rock-stable overall.
As you can see with #8722 and #7759 I've been starting to bump against the restrictions of 2.0.x. So I'm in favor for this.
(Note: This issue should be reopened, as the tasks in op are not yet addressed, I think)
On Wed, Jan 11, 2017 at 1:56 PM, Wladimir J. van der Laan < notifications@github.com> wrote:
Closed #8867 https://github.com/bitcoin/bitcoin/issues/8867 via #9471 https://github.com/bitcoin/bitcoin/pull/9471.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/bitcoin/bitcoin/issues/8867#event-919058559, or mute the thread https://github.com/notifications/unsubscribe-auth/AGGmv3iZ9jr5PkejNjXFu4NKash3UQTIks5rRNGVgaJpZM4KMaCV .