> Oh, and just to clarify, in the case of 4.19.1.1, we did _not_ intend to
> update the translations in that release at all, which is why this issue
> wasn't caught yet.
Just FTR: updating translations should be be part of the (pre)release process.
Email addresses taken from each .po files should be used to spread
notifications "I'm going to release new version of software X in next N days.
Please update translations". This shuld be predeceased by `make -C po
update-po` and commit to the all .po files.
As long as translations are kept in separated repo it makes that harder to sync
and to keep track of all changes between version (because tag repo A do not
causes that such tag is propagated across submodule).
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2899#issuecomment-1954541111
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2899/1954541...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
