Simplify tag file and history creation
Currently, when a new release is cut, the information about the solved issues must be entered both in the tags.txt file and in history.hml.
Would be nice to have a single input able to generate both.
#1 Updated by Marco Mambelli 15 days ago
- Target version changed from v3_6_2 to v3_6_1
- Assignee changed from Marco Mambelli to Lorena Lobato Pardavila
- Status changed from New to Feedback
The tags and history will be generated starting form a yaml file: tags.yaml
The conversion is done by a python3 tool: process_tags.py
This will be used for future releases.
changes are in v35/23304