The problem is packages don't use this consistently, and don't even make an effort to tell us of breaking changes. 0.x.x is supposed to mean, and often does mean, the package is in a period of rapid API breakage. But many packages simply use it as an excuse to break their API whenever they want. Node.js itself, Jade, Mongolian have all introduced more than one breaking change *as a bugfix, patch release increment.* There's absolutely no way to future-proof these dependencies, except to regularly check for updates, and either blacklist the breaking patch numbers as they're released, or upgrade your application accordingly. This is a waste of time and effort that could easily be avoided.
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. On Thursday, September 20, 2012 11:30:44 AM UTC-7, Scott González wrote: > > On Thu, Sep 20, 2012 at 2:27 PM, Austin William Wright < > [email protected] <javascript:>> wrote: > >> The problem comes in when I or other developers want to *use* those >> libraries, and keep them up-to-date. You can't use features like "~1". >> > > You know when you're using a module that's in a 0.x release cycle, so just > use ~0.y.z and you'll be fine. > -- 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
