By this formula, Node has been 1.0+ since day one and never broken backwards compatibility... Its understandable that young projects hover below 1.0 in order to get a more throughly designed API in place (and maybe fix/remove API kinks that were bad ideas at one point in time)... but some would say that 3+ years is kinda pushing that safety net for such a largely used project...
Essentially anyone familiar with semver would be leery of using Node for a large scale application with the lack of guarantee in backwards compatibility (or they should be without better explanation of the "Node way" of doing things). -Karl Tiedt On Thu, Sep 20, 2012 at 1:24 PM, Tim Caswell <[email protected]> wrote: > To convert > node-community-style semver numbers to "official" semver numbers, use > this table. > > 0.0.x -> 0.0.x > x.y.z -> (x + 1).y.z > > So 0.3.14 would be 1.3.14 and 0.0.14 would stay 0.0.14. > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
