Well yeah, *ideally* you'd have an official string freeze period with
translation notifications for major releases. And ideally you'd also have
per-release branches for translations because over time they grow different so
you can't safely pull updated translations to stable releases.
Why we never did that? Because it's just too much hassle for the benefit, for a
tool like rpm.
This ticket is a bit funny because we don't *have* any "update-po" target at
all. There's just "update-pot". The ticket summary talks about -po, the initial
post about -pot and then later again -po, so it's kinda hard to tell what is
actually meant by that.
In any case, "update-pot" *should* be functional in git master, and be run
during alpha/beta/final releases of a new major release. I updated the po
submodule just now to pull in the path changes at least, but the current
POTFILES.in approach is not sustainable, that needs to change to something like
"any *.c files". However "update-pot" (and consequent push) should NOT be run
from stable releases because there's no corresponding branch in the
translations.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2899#issuecomment-1956026332
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2899/1956026...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
