<commit_before>Contributing
============

The BigBang community welcomes contributions.

[TODO port in from README.]<commit_msg>adding release procedure, including pip freeze, fixes #176<commit_after>Contributing
============

The BigBang community welcomes contributions.

Release Procedure
--------------------

When the community decides that it is time to cut a new release, the Core Developers select somebody to act as release manager.
That release manager then performs the following steps.

1. Determine the next release number via the standards of semantic versioning.
2. Solicit a worthy name for the release.
3. Address any remaining tickets in the GitHub milestone corresponding to the release, perhaps moving them to other milestones.
4. Consult the GitHub records of merged PRs and issues to write release notes documenting the changes made in this release.
5. If the dependencies in main are not already frozen, use ``pip freeze`` to create a new frozen dependency list. Consider testing the code against unfrozen dependencies first to update version numbers.
6. Use the `GitHub Releases interface <https://github.com/datactive/bigbang/releases>`_. to cut a new release from the main branch, with the selected name and number. This should create a new tag corresponding to the release commit.
7. Write a message to the BigBang development list announcing the new release, including the release notes.
{'fraction_non_alphanumeric': 0.0685512367491166, 'fraction_numerical': 0.007067137809187279, 'mean_word_length': 4.552941176470588, 'pattern_counts': {'":': 0, '<': 4, '<?xml version=': 0, '>': 4, 'https://': 1, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7280880', 'n_tokens_mistral': 332, 'n_tokens_neox': 313, 'n_words': 198}