The Release Notes Application 2.4, 2.4.1, 2.5 and 2.6 have been released.
These releases bring the following changes:
2.4
- The release note and change lists now use Live Data instead of the deprecated LiveTable
- The application can be configured from the Administration UI (default product and default release note template)
- The "with screenshots" and "without screenshots" report filters can be unchecked again
- The report and displayer parameters of the getChanges and displayChanges macros are handled more consistently
- The greater-or-equal and lower-or-equal version filters of getChanges now really include the bounds
- Editing the configuration page no longer requires force editing
- Enforcing script right on the release note template now also enforces it on the created page
- Raises the minimal supported XWiki version to 17.10, the current LTS cycle
2.4.1
- The release note template page no longer displays raw Velocity code as its title
- The Release Changes Live Data no longer overflows the page: the Summary column is visible again and the Title column no longer wraps mid-word
- Fixes the Administration category, the default product name and the missing field hints of the configuration UI
- Upgrading from a previous version now adds the Administration section
2.5
- Screenshots can be added and modified directly while editing a change
- In a list of changes, the screenshot is now displayed right after the change title
- The "Add ... Change" buttons no longer redirect to the deprecated inline action, which only exists in the legacy module
- The Summary column of the Release Changes Live Data can be added back from the Properties panel
- Only the first video of a change is displayed in the grid layout, instead of all of them
- Removes the intrusive "Configure the Release Notes Application" link from the application home page
2.6
- Two authors adding a change to the same release note at the same time are no longer given the same entry page, so the second save cannot overwrite the first
- The version range filters of getChanges compare versions as versions instead of as strings
- The getChanges query is executed with a limit and its results are no longer each loaded as a full document
- All the strings displayed by the application now come from its translation bundle instead of being hardcoded in English
- The text inputs of the release note, change and report forms have an accessible name, and the product field has a placeholder
- The Release Changes Live Data of the home page is sorted by creation date again
- The application's pages no longer resolve their top-level space at runtime, which also removes a query injection vector
