<commit_before>=================
Release checklist
=================

Checklist for ordinary releases
===============================

* Git branch naming note

  - ``vN.N.N-release-prep``: use this naming for bumping version number, etc.
    Merge to master before tagging release.

  - ``vN.N.N-release-post``: use this naming for bumping version number after
    release, checklist fixes after release, etc.

* Git maintenance

  - ensure git commits are up-to-date

  - ensure branches are merged, unused branches deleted (also remotely)

  - ensure branches are rebased where applicable

  - git fsck --full

  - git gc --aggressive

* Finalize DUK_VERSION

  - Change previous development version (with patch level 99) to release
    version

  - Verify by running Duktape cmdline and evaluating ``Duktape.version``

* Check dist-files/README.rst

* Ensure LICENSE.txt is up-to-date

  - Check year range

* Ensure RELEASES.rst is up-to-date (must be done before candidate tar.xz
  build because dist package contains RELEASES.rst)

  - New release is in place

  - Release date is in place

* Ensure tests/api/test-all-public-symbols.c is up-to-date

  - Must add all new API calls
<commit_msg>Release checklist update<commit_after>=================
Release checklist
=================

Checklist for ordinary releases
===============================

* Git branch naming note

  - ``vN.N.N-release-prep``: use this naming for bumping version number, etc.
    Merge to master before tagging release.

  - ``vN.N.N-release-post``: use this naming for bumping version number after
    release, checklist fixes after release, etc.

* Git maintenance

  - ensure git commits are up-to-date

  - ensure branches are merged, unused branches deleted (also remotely)

  - ensure branches are rebased where applicable

  - git fsck --full

  - git gc --aggressive

* Finalize DUK_VERSION

  - Change previous development version (with patch level 99) to release
    version

  - Verify by running Duktape cmdline and evaluating ``Duktape.version``

* Check dist-files/README.rst

* Ensure LICENSE.txt is up-to-date

  - Check year range

  - Also check ``util/create_spdx_license.py``

* Ensure RELEASES.rst is up-to-date (must be done before candidate tar.xz
  build because dist package contains RELEASES.rst)

  - New release is in place

  - Release date is in place

* Ensure tests/api/test-all-public-symbols.c is up-to-date

  - Must add all new API calls

{'fraction_non_alphanumeric': 0.12393336042259244, 'fraction_numerical': 0.0016253555465258025, 'mean_word_length': 3.4845173041894353, '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': '1971478', 'n_tokens_mistral': 746, 'n_tokens_neox': 689, 'n_words': 275}