I think one way we disagree is in the definition of "standard". All npm guarantees is that the version by *parseable* by node-semver, not that they follow the complete semver specification.
It may not be a documented "standard", but what Tim alludes to, architecture-change.breaking-change.non-breaking-change, is a common practice. Schoon -- 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
