Skip to content

releasing.md

Latest commit

 

History

History
25 lines (21 loc) · 1.7 KB

releasing.md

File metadata and controls

25 lines (21 loc) · 1.7 KB

Release process

To create a release, follow the below steps.

Release preparation

  • Create a draft of a Release with a new tag number vX.Y.X sourced from the develop branch on github releases page
  • Populate release description using the Generate release notes button
  • Review the auto-generated release notes and update tem if needed
  • Optionally, split the default ## What's Changed list into ## New features, ## Enhancements, ## Bug fixes. See previous release notes for details

Performing a release

  • Publish the previously prepared release draft.
  • Wait for the Github Actions Release process to complete successfully. The process will do the following:
    • create a new tag
    • generate html documentation to be included in the release file.
    • publish documentation for the new version into utPLSQL site
    • upload release artifacts (zip and tar.gz files along with sha256 files)
    • update the CHANGELOG.md file with the release details
    • publish an announcement about the release in the utPLSQL Organization Discussions
    • publish a release post on utplsql.github.io (new post in docs/_posts, updated mkdocs.yml nav and docs/index.md)
  • After the release process is finished, manually increase the version number in the VERSION file on develop branch to start the next release version.
  • Send an announcement about the release on:Twitter(X), BlueSky, LinkedIn account about the utPLSQL release.

Note:

The release artifacts include HTML documentation generated from MD files, sources and tests