[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [Libevent-users] When will libevent 2.x be released?
- To: libevent-users@xxxxxxxxxxxxx
- Subject: Re: [Libevent-users] When will libevent 2.x be released?
- From: Nick Mathewson <nickm@xxxxxxxxxxxxx>
- Date: Wed, 14 Apr 2010 14:40:39 -0400
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: libevent-users-outgoing@xxxxxxxx
- Delivered-to: libevent-users@xxxxxxxx
- Delivery-date: Wed, 14 Apr 2010 14:40:49 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:received:message-id:subject :from:to:content-type; bh=N+H89yQzZoc9F8oPq+pw7iUDb3nR7uHQ4UIfZ7uGrfM=; b=qnI7k3sFGwGHDH01zhNPasHSdGIqVrvaE7tRMIBDMhqEyFkqpl2h+BiFfDhM/qjoI5 NecWcGaaNMaZyt15Z6Zw+ajQyBHM/5RiMlly8pek6RQNoYr+Q3ZH/W9fDWQiSGs12BfV NkX4p5WlwavBUqqeoem2RNwV8YDrt5NuAJg20=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=njkDQNZc+jK/gHvZ4j8MYxiJMUrK2rkCJq1gpnlGsq3tT3xTuBeQwJdc7w7TSUFJwT FrGDP19b8qG/SI5tjgHZV7O57xeU0TUjbvB1trWsURdXQE41It428qgF+SObPF4BEAR9 IqXdsmB8/zrFekQN0ZJfTU5yA2uwS0tablC7I=
- In-reply-to: <1271210638.21881.28.camel@localhost>
- References: <1271210638.21881.28.camel@localhost>
- Reply-to: libevent-users@xxxxxxxxxxxxx
- Sender: owner-libevent-users@xxxxxxxxxxxxx
On Tue, Apr 13, 2010 at 10:03 PM, Angus Salkeld <asalkeld@xxxxxxxxxx> wrote:
> Hi
>
> We are quite keen to use libevent for corosync (corosync.org)
> but wish to use the 2.x branch as our daemon is very threaded.
>
> When do you hope to release the 2.x branch?
>
> Note: there is no pressure we just want to plan when to do this work.
I was hoping for the first quarter of 2010, but that seems unlikely
unless the Python developers lend us their time machine. ;)
Failing that, I'd be quite sad if the release candidate for 2.0.x
comes out later than May. If this means pushing features out to
Libevent 2.1, so be it; with luck, Libevent 2.1 will have a much
shorter development cycle than 2.0. Fortunately, Git makes it pretty
easy for us to hold off on merging code that isn't ready until it
really is ready for integration.
Our current tentative schedule (assuming I didn't misunderstand my
last conversation with Niels and Chris) is to declare a feature freeze
for the end of April and try to get a release candidate out by the end
of May.
> Do you think this will make it into Fedora 14?
I have no idea; I don't know Fedora policies. The Fedora maintainers
would probably be better people to ask about that.
--
Nick
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users in the body.