Hi all, Remember we said 0.12 was around the corner? Well, the release is, but it won't be 0.12.0, it will be 1.0.0 instead.
Why the change? APIs have changed and evolved in libuv, but the core design has remained the same since its inception, for the most part. We have entities represented as handles and operations represented as requests. Long running or continuous operations are triggered with some *_start function and stopped with some *_stop function. This hasn't changed. We believe the current design is mature enough to call it 1.0.0 and support it for an extended period of time. APIs will be allowed to evolve as per SemVer (semver.org) and ABI will remain stable throughout the 1.x series of libuv. So, what's next then? libuv 1.x will continue to evolve as per the current design, but we'll start working on what will eventually become libuv 2.0.0, which refines the design and (hopefully) fixes certain areas where currently libuv falls short. Thanks to everyone who helped libuv get to it's current state, <3. Cheers, -- Saúl Ibarra Corretgé bettercallsaghul.com
signature.asc
Description: OpenPGP digital signature
