<commit_before>Midnight dynamite release steps
===============================

Release steps for
[midnight_dynamite](https://github.com/gradha/midnight_dynamite).

* Create new milestone with version number (``vXXX``) at
  https://github.com/gradha/midnight_dynamite/issues/milestones.
* Create new dummy issue `Release versionname` and assign to that milestone.
* ``git flow release start versionname`` (versionname without v).
* Update version numbers:
  * Modify [README.md](../README.md) (s/development/stable/).
  * Modify [midnight_dynamite.nim](../midnight_dynamite.nim).
  * Modify [midnight_dynamite.babel](../midnight_dynamite.babel).
  * Update [docs/changes.md](changes.md) with list of changes and
    version/number.
* ``git commit -av`` into the release branch the version number changes.
* ``git flow release finish versionname`` (the tagname is versionname without
  ``v``).  When specifying the tag message, copy and paste a text version of
  the changes log into the message. Add md item markers.
* Move closed issues to the release milestone.
* ``git push origin master stable --tags``.
* Increase version numbers, ``master`` branch gets +0.0.1.<commit_msg>Updates release steps. Refs #19.<commit_after>Midnight dynamite release steps
===============================

Release steps for
[midnight_dynamite](https://github.com/gradha/midnight_dynamite).

* Create new milestone with version number (``vXXX``) at
  https://github.com/gradha/midnight_dynamite/issues/milestones.
* Create new dummy issue `Release versionname` and assign to that milestone.
* ``git flow release start versionname`` (versionname without v).
* Update version numbers:
  * Modify [README.md](../README.md) (s/development/stable/).
  * Modify [midnight_dynamite.nim](../midnight_dynamite.nim).
  * Modify [midnight_dynamite.babel](../midnight_dynamite.babel).
  * Update [docs/changes.md](changes.md) with list of changes and
    version/number.
* ``git commit -av`` into the release branch the version number changes.
* ``git flow release finish versionname`` (the tagname is versionname without
  ``v``).  When specifying the tag message, copy and paste the
  markdown version of the changes log into the message.
* Move closed issues to the release milestone.
* Increase version numbers, ``master`` branch gets +0.0.1.
{'fraction_non_alphanumeric': 0.13989637305699482, 'fraction_numerical': 0.0034542314335060447, 'mean_word_length': 4.735148514851486, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, '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': '75845', 'n_tokens_mistral': 688, 'n_tokens_neox': 665, 'n_words': 229}