Message sharing: rename certain existing templates
Registered by
Jeroen T. Vermeulen
Some templates have version numbers in their names, e.g. evolution-2.2. Those won't benefit from message sharing. We should give them uniform names, e.g. plain "evolution" before running the migration script that will unify duplicated messages between matching templates.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- High
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Данило Шеган
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- 2.2.6
- Started by
- Данило Шеган
- Completed by
- Данило Шеган
Related branches
Sprints
Whiteboard
Looked over products templates, only a few that need any action: https:/
Need to prepare a suitably usable list for Ubuntu, include sourcepackage, potemplate, messagecount, distroseries there.
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.