<commit_before>This is the procedure to do for each release.

There are three sections:

* BEFORE: To prepare the release.
* PERFORM: Tasks that conform the release.
* AFTER: Once the release has been done, some extra tasks to prepare the env.

BEFORE

* To change the version variable in the code (AdminHeader):
https://github.com/angoca/log4db2/blob/master/src/main/sql-pl/AdminHeader.sql
* Change the version in the documentation (@version) of all source files.
* Make sure the schema reflects the version number to release (all files.)
* Perform last commit and push.

PERFORM

* To performa a code release in GitHub (https://github.com/angoca/log4db2/releases)
* To create a directory in SourceForge with the version to release as name.
* To execute mvn.
* To publish the generated files in the target directory, into the just created directory in SourceForge.

AFTER

* To change the schema name to the new version is all files.
* Test that there are not references to the previous release.
<commit_msg>Minor changes<commit_after>This is the procedure to do for each release.

There are three sections:

* BEFORE: To prepare the release.
* PERFORM: Tasks that conform the release.
* AFTER: Once the release has been done, some extra tasks to prepare the env.

BEFORE

* To change the version variable in the code (AdminHeader):
https://github.com/angoca/log4db2/blob/master/src/main/sql-pl/AdminHeader.sql
* Change the version in the documentation (@version) of all source files.
* Make sure the schema reflects the version number to release (all files.)
* Perform last commit and push.

PERFORM

* Perform a code release in GitHub (https://github.com/angoca/log4db2/releases)
* Create a directory in SourceForge with the version to release as name.
* Execute mvn.
* Publish the generated files in the target directory, into the just created
  directory in SourceForge (change the button text) and in GitHub.
* Delete the current README.txt from SourceForge. Upload the current version
  of README.txt

AFTER

* Change the current development status in source forge 
* To change the schema name to the new version is all files.
* Test that there are not references to the previous release.
* Commit these changes and publish.

{'fraction_non_alphanumeric': 0.062275985663082435, 'fraction_numerical': 0.0035842293906810036, 'mean_word_length': 4.2172897196261685, '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': '1034620', 'n_tokens_mistral': 610, 'n_tokens_neox': 599, 'n_words': 311}