Skip to content

Latest commit

 

History

History
38 lines (23 loc) · 1.62 KB

release.md

File metadata and controls

38 lines (23 loc) · 1.62 KB

Release (CoreMedia-only)

[Up] [Top]

Table of Content

  1. Release Steps
  2. Post Process

Release Steps

  • Make sure that all dependencies to CoreMedia core artifacts only use <scope>provided</scope> or <scope>runtime</scope> so that these non-public artifacts are not accidentally included in the resulting ZIP file.

  • Ensure you have built the CMCC version (snapshot versions) which this workspace dedicates to. Otherwise, the third-party versions won't match the declared CMCC version (most third-party dependencies) are managed in Blueprint and CMCC Core.

  • Update THIRD-PARTY.txt and license downloads either manually or by running if you are using Maven and Java:

    $ mvn -Pdocs-third-party generate-resources

  • Update badges at main workspace README.md.

  • Update the CHANGELOG.md.

  • Use Create new release with a proper name for the tag, a release title that matches the other releases, and a description that matches the changelog. The GitHub action will then attach the Plugin artifacts to the release.

Post Process

  • Review GitHub issues and possibly adjust state.
  • Close and possibly rename the milestone.