Include translation scripting modules in Frameworks tarballs (2)
Review Request #121524 - Created Dec. 14, 2014 and submitted
Currently, the release script expects that the name of framework and translation scripting module are same, plus 5 (e.g. ki18n and ki18n5 catalog/module), and tries only to include the module of that name. Instead, it should check for each detected PO file whether there is a corresponding scripting module (e.g. plasma-framework but libplasma5 catalog/module).
Run update_l10n.sh and make_rc_tag.sh on few frameworks which have a scripting module and equal or different name and catalog name.