If more than a dozen people are using your package, then next time you make a breaking change, release 1.0.0. Continue to clearly identify when you make breaking changes, when you release new features, and when you release a patch.
That'd help tremendously with the package ecosystem, I believe. Certainly it'd help me. On Thursday, September 20, 2012 12:16:07 PM UTC-7, Rick Waldron wrote: > > On Thu, Sep 20, 2012 at 3:10 PM, Austin William Wright < > [email protected] <javascript:>> wrote: > >> 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. >> >> > What is the end game? Were you hoping to get everyone to smarten up, see > the error of their ways and change all of their package.json files? > > This is a serious question. > > > -- 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
