The API *does not need to be *what you definitely want. If you decide to later change the API, just release 2.0.0. The important part is that you tell us clearly that the API broke. That's all that matters.
On Thursday, September 20, 2012 12:04:10 PM UTC-7, Scott González wrote: > > On Thu, Sep 20, 2012 at 2:59 PM, Austin William Wright < > [email protected] <javascript:>> wrote: > >> Also if you're releasing versions with a 0. prefix then what's the point? >> You're dropping the indication of new feature releases, just so you can >> have a leading 0.? This inconsistency is confusing and unnecessary. >> > > You can easily use 0.x.y where x = new features/breaking changes and y = > bug fixes. The reason for using 0.x is to indicate that you have not > decided that the API is what you definitely want. While x and y in 0.x.y > have no meaning in semver, they can and often do have meaning in the real > world. > > Whether people take this too far is a separate question. But at this point > you're arguing in black and white and that's just not how the ecosystem > actually works. > -- 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
