Simpler msg when namespace is identical to filename except -/_
Link to Clojars for Maven and Gradle dependency syntax
Copy README.md to README.next.md, in prep of updating .next.md
Fix #104 - add :warning-output-file option
Add post-0.1.5 change descriptions
Fix #97 - add new linter :unused-meta-on-macro
Beginning of implementation of :constant-test linter

It does not yet correctly handle the bindings involved in these macros:

if-let when-let and or when-first if-some when-some

Those all have test cases in constanttestexpr.clj, marked tbd.
Some massaging of :constant-test linter

Looking towards adding good warnings for bindings soon.
Additions and refinements to :constant-test linter

It has been run on all current projects in crucible.  No crashes, and
most of the warnings look reasonable.  I disabled them for Carmine and
core.match because they have some macros and/or tests that cause
hundreds of :constant-test warnings to be produced.  Definitely would
be nice to have a way to disable the warning inside of particular
macro definitions, and have that disabling survive the macroexpansion
process.
Update changes.md for :constant-test linter
Prepare for tagging version 0.2.0-alpha1
Change versions back to 0.2.0-SNAPSHOT for further development
Work on a branch towards making suspicious-expression based on asts only

This should eliminate at least some undesired :suspicious-expression
warning messages for forms like (-> 1 (= 1)).

I also believe that once all but a tiny fraction of linters are using
the asts and not the source code text or read-in forms, it will be
easier to have 1 way to suppress warnings on a per-expression basis
via source code annotations (e.g. in metadata).  Trying to devise an
implementation that works for linters that use text or read-in forms
as well sounds like a pain.
Looking good, except for an issue with and/or

It looks like and/or with >= 2 args will warn all of the time, because
the macroexpansion on the 'way down' includes an expression of the
form (and x).  Need to figure out a correct way to suppress this.
Prevent :suspicious-expression warnings for normal and/or uses
Eliminate some unwanted warnings for updated suspicous-expression linter

In particular, for suspicious-looking expressions that arose during
the macro expansion of and, or, cond, and defrecord forms.
Test level 4 headings in Github flavored Markdown
Looks like all text must go on same line to be part of same heading
Try new shorter links for linters in README.next.md
Missed :def-in-def linter heading.  Add :unused-namespaces section