Just so my aching head can try to understand: libevent doesn’t follow libtool numbering schemes. Thus, a “release” numbered 2.1.5 isn’t actually ever going to be really released - it’s just some numbered stake-in-the-ground prototype that users use at their own risk.
Actual “releases” are numbered tarballs that have a “-stable” on the end of them to indicate some level of testing beyond “beta". These are now several years out-of-date, and the path forward appears to be somewhat uncertain given how long things have been stalled at “beta”. Does that pretty much summarize the situation? I’m not being critical - just trying to understand all the confusion that is swirling around when an updated version might become available. Ralph > On Oct 25, 2016, at 2:06 PM, Azat Khuzhin <[email protected]> wrote: > > On Mon, Oct 24, 2016 at 11:36 PM, Sanjiv <[email protected]> wrote: >> Hi Libevent owners, >> >> Is there any plan to promote 2.1.5 from beta to stable ? 2.1.5-beta was >> released in Jan 2015 . I'm also interested in knowing what factors are >> considered from promoting a release from beta to stable. > > Hi Sanjiv, > > Well 2.1.5 will not be stable anyway, but 2.1.7 will be (*I hope*), as > for *When* I hope that in a month or so. > > For more info you can take a look at: > https://github.com/libevent/libevent/issues/285 # 2.1 > https://github.com/libevent/libevent/issues/348 # 2.0 > > Cheers, > Azat. > *********************************************************************** > To unsubscribe, send an e-mail to [email protected] with > unsubscribe libevent-users in the body. *********************************************************************** To unsubscribe, send an e-mail to [email protected] with unsubscribe libevent-users in the body.
