<commit_before>Steps to prepare in making a new release:

Change any snapshot versions of dependencies in project.clj to
non-snapshot versions.

Redo any unit tests 'lein test', and check for any changes in
behavior.  Compare against output of previous release.  Update
changes.md and changes-detailed.md with any differences in behavior.


Places where version number should be updated:

* project.clj just after jafingerhut/dolly
* README.md in install instructions, and instructions for developers
* src/leiningen/dolly.clj var dolly-version-string

Update the change log in changes.md

Commit all of those changes.

Tag it with a version tag, e.g.:

    % git tag -a dolly-0.1.0

I don't put much into the commit comments other than 'Dolly version
0.1.0'

'git push' by default does not push tags to the remote server.  To
cause that to happen, use:

    % git push origin --tags

Then deploy a release to Clojars.org:

* TBD: Add instructions for that here, including the potentially
  longer 'what was needed to do it the first time', perhaps later
  below.


When that is complete, then pick the next version number, at least a<commit_msg>Update to doc<commit_after>Steps to prepare in making a new release:

Change any snapshot versions of dependencies in project.clj to
non-snapshot versions.

Redo any unit tests 'lein test', and check for any changes in
behavior.  Compare against output of previous release.  Update
changes.md and changes-detailed.md with any differences in behavior.


Places where version number should be updated:

* project.clj just after jafingerhut/dolly
* README.md in install instructions, and instructions for developers
* src/leiningen/dolly.clj var dolly-version-string

Update the change log in changes.md

Commit all of those changes.

Tag it with a version tag, e.g.:

    % git tag -a dolly-0.1.0

I don't put much into the commit comments other than 'Dolly version
0.1.0'

'git push' by default does not push tags to the remote server.  To
cause that to happen, use:

    % git push origin --tags

Then deploy a release to Clojars.org:

    % lein deploy clojars


When that is complete, then pick the next version number, at least a
{'fraction_non_alphanumeric': 0.05601469237832874, 'fraction_numerical': 0.005509641873278237, 'mean_word_length': 3.8101545253863134, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3932794', 'n_tokens_mistral': 632, 'n_tokens_neox': 615, 'n_words': 316}