Hi all, So, a bit of a snafu in the release process. I merged in a not-quite-ready PR and had to do an immediate patch release. Here are the release notes:
0.6.0: http://eslint.org/blog/2014/05/eslint-0.6.0-released/ 0.6.1: http://eslint.org/blog/2014/05/eslint-0.6.1-released/ 0.6.0 turned out to be a much bigger release than I had hoped for. Going forward, I'm going to try to keep releases smaller to manage the risk better. Also, I drafted some new contribution guidelines: http://eslint.org/docs/developer-guide/contributing.html The biggest changes are a standard commit message format and asking people to squash commits on PRs. These are important to help create release notes automatically (I'm doing it by hand now, and it sucks). A big theme that came out of this release is the fragility of ignored files and rules settings priority across files and directories. These are two important parts of ESLint that are not working correctly and likely have to be rewritten from scratch to stop the bleeding. I'm going to see what can be done to clean out a bunch of these bugs in one swoop. As always, thanks for your help and feedback. -- ______________________________ Nicholas C. Zakas @slicknet Author, Professional JavaScript for Web Developers Buy it at Amazon.com: http://www.amazon.com/Professional-JavaScript-Developers-Nicholas-Zakas/dp/1118026691/ref=sr_1_3 -- You received this message because you are subscribed to the Google Groups "ESLint" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
