<commit_before>
While we are not using maven-release, this is how to make a release.
Note: it is important to do these steps in exactly this order.

1. inside local clone of repo prepare the sourceforge git repo:

- update CHANGELOG.txt
- update scripts/create_repo.sh and scripts/create_dependency_repo.sh
  (if there was an update in dependencies)
- mvn clean
- mvn release:prepare
  _IMPORTANT_ choose version X.Y as the release tag name

2. prepare the release tarball:

- check out the release tag into separate directory called hadoop-bam-X.Y
- mvn package
- copy target/hadoop-bam-X.Y.jar and *-with-dependencies.jar into root
  directory, then delete target, scripts/, other files such as .git
- create tarball hadoop-bam-X.Y.tar.gz and upload tar.gz and README.txt to
  sourceforge (make sure to press "i" on file and select "all OS" so that
  it appears under the latest release link)

3. update the maven repo on sourceforge website:

- run scripts/create_repo.sh (and scripts/create_dependency_repo.sh if
  necessary)
- these will create files inside /tmp (a local maven repo)
- sftp local maven repo to sourceforge, path on ftp server:
  /home/project-web/hadoop-bam/htdocs/maven
  _Note_: you may need to manually delete old directories, such as
  6.2-SNAPSHOT after uploading 6.2 release
<commit_msg>Updating HOWTO_release<commit_after>
- mvn clean package
- mvn release:prepare
- mvn release:perform
- login here: https://oss.sonatype.org/
- First close staging repo, then release it
- Done 
{'fraction_non_alphanumeric': 0.07033842070338421, 'fraction_numerical': 0.0046449900464499, 'mean_word_length': 3.896103896103896, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 1, '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': '1255413', 'n_tokens_mistral': 475, 'n_tokens_neox': 454, 'n_words': 197}