## :white_check_mark: Summary 1. [Minimum Jahia version](#user-content-minimum-jahia-version) 2. [Testing matrix](#user-content-testing-matrix) 3. [Prepare checklist](#user-content-prepare-checklist) 4. [Tests checklist](#user-content-test-checklist) 5. [Publication checklist](#user-content-publication-checklist) <h2 id="minimum-jahia-version">Minimum Jahia version</h2> > We aim at reducing the possible deployment matrices by regularly bumping up the minimum Jahia version when releasing new versions of our modules. When creating a Release ticket for a module, consult with your PM to identify the new minimum Jahia version this module must be associated with. The default guideline is for a new module release to be compatible with the 2 previous releases. Current Jahia Version: 8.2.1.0 (version currently in the POM) Desired Jahia Version: 8.2.1.0 <h2 id="testing-matrix">:scroll: Testing matrix</h2> <h3> Notes for release testing:</h3> See https://github.com/Jahia/javascript-modules/releases/tag/untagged-59c41363aa1aaadfe2aa. You can reach out to @GauBen for more details. <h3>Version matrix</h3> > We aim at clearly documenting the possible deployment scenarios in a matrix and specify which ones are expected to be tested or not. In the testing matrix, always use the latest patch version of a particular release The following combinations should be validated: - 8.2.1.0 - 8.2.2.1 :information_source: If you are releasing for the main branch of a module, make sure to complete the checklist below when working on the ticket. <h2 id="prepare-checklist">:pencil2: Prepare checklist</h2> - [x] All other tickets within that milestone are are closed - [x] Testing matrix and Minimum Jahia version are detailed - [x] Jahia-parent (minimum Jahia version) was updated if requested in the ticket - [x] Release creation has been triggered from the Github Release UI ([detailed documentation](https://jahia-confluence.atlassian.net/wiki/spaces/PR/pages/2064804/Releasing+a+module#Releasingamodule-ReleasingwithGithub)) <h2 id="tests-checklist">:vertical_traffic_light: Tests checklist</h2> General - [x] Manual tests detailing testing steps for validating the release of this module are present on Testrail - [x] Automated tests using the release artifacts were executed against the oldest and newest release of Jahia Module migration - [x] Upgrade from the previous released version of the module was tested - [x] The upgrade did not require clearing the browser cache (i.e. missing labels) While Testing - [x] No warnings or errors are present in the browser console when testing the module - [x] No warnings or errors are present in Jahia logs when testing the module (incl. migration) - [ ] Select a random set of fixes from the release and verify them on the minimum jahia-version After Testing - [x] Tested combinations (Jahia versions, modules versions) are listed in this released ticket - [ ] ~~Tested scenarios not detailed in Testrail are listed in this release ticket~~ - [ ] ~~The version was updated in the [Selenium integration tests](https://github.com/Jahia/jahia-qa/blob/f4f788d56fd624174302231e3d64878cd343e515/pom.xml#L75)~~ <h2 id="publication-checklist">:rocket: Publication checklist</h2> - [x] The release changelog was prepared - [x] In case of a major release, a **Breaking Changes** section is present in the Changelog - [x] The artifact was released on Nexus - [x] If the module is included in Jahia distribution, [jahia-pack-private](https://github.com/Jahia/jahia-pack-private/blob/master/core-modules/pom.xml) was updated with the released version - [x] If applicable, corresponding academy pages were published - [x] The module was published on the store - [x] The [modules releases log page](https://edit.jahia.com/jahia/jcontent/academy/en/pages/home/customer-center/jahia/release-notes/modules-releases-log?params=(sub:!f)) on the Academy was updated - [x] A message was published on slack #releases channel - [ ] The milestone on GitHub was closed