Send in pot files too - they're merged automatically with all the .po
files in the TP.
In fact, this has been the case for the bison-runtime domain, as it
rarely sees changes. I get notified that there's a new version but it
just stays fully translated so there's no work for me.
Since bison tends to get alpha releases, I guess the easiest way to
ensure an up-to-date translation would be to ensure that a release
must
always be based on a previous alpha release (with the only changes
being
the version number). That way, there cannot be any change in the pot
file either.
As long as there is sufficient time between the last alpha and the
release (I'd say a week would be enough, but I don't know how quickly
the average translator updates a po file after being notified), this
would mean that the translations will have been mostly updated for the
alpha and will then be readily usable for the release too.