Release javascript-modules 0.8

[GauBen]

✅ Summary

1. Minimum Jahia version
2. Testing matrix
3. Prepare checklist
4. Tests checklist
5. Publication checklist

Minimum Jahia version

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

📜 Testing matrix

Notes for release testing:

Please add all relevant hints which can help QA when testing the release - for module releases on the main branch, this might be obsolete. For releases on the maintenance branch consider the following topics:

• expected automated tests
• scope of the release (simple backport vs. different implementation of a fix)

Nothing specific for JSM, all features have been tested in alpha builds. All QA efforts should be focused on Luxe.

Version matrix

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:

• Jahia 8.2.1.0 (according to the pom.xml)

ℹ️ If you are releasing for the main branch of a module, make sure to complete the checklist below when working on the ticket.

✏️ Prepare checklist

• All other tickets within that milestone are are closed
• Testing matrix and Minimum Jahia version are detailed
• Jahia-parent (minimum Jahia version) was updated if requested in the ticket
• Release creation has been triggered from the Github Release UI (detailed documentation)

🚦 Tests checklist

General

• Manual tests detailing testing steps for validating the release of this module are present on Testrail
• Automated tests using the release artifacts were executed against the oldest and newest release of Jahia

Module migration

• Upgrade from the previous released version of the module was tested
• The upgrade did not require clearing the browser cache (i.e. missing labels)

While Testing

• No warnings or errors are present in the browser console when testing the module
• 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

• 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

🚀 Publication checklist

• The release changelog was prepared
• In case of a major release, a Breaking Changes section is present in the Changelog
• The artifact was released on Nexus
• If the module is included in Jahia distribution, jahia-pack-private was updated with the released version
• If applicable, corresponding academy pages were published
• The module was published on the store
• The modules releases log page on the Academy was updated
• A message was published on slack #releases channel
• The milestone on GitHub was closed

[GauBen]

QA done through Luxe, which incorporates the new 0.8 features