[wp-meta] [Making WordPress.org] #6188: Language Pack generation: trigger on plugin update
Making WordPress.org
noreply at wordpress.org
Fri Apr 15 15:10:35 UTC 2022
#6188: Language Pack generation: trigger on plugin update
--------------------------------------+---------------------
Reporter: adamsilverstein | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Translate Site & Plugins | Resolution:
Keywords: |
--------------------------------------+---------------------
Comment (by adamsilverstein):
> If all we need to do is delay that update (to prevent people from
starting to get the new version) until translations are ready,
We gave this a try and it failed. The language packs were not generated
until we pushed the plugin version update (the tagging didn't trigger
language pack regeneration).
@ocean90 or @dd32 - would it possible to trigger language pack
regeneration when a new tag is added - that way we could trigger the
update before pushing the plugin update itself.
Note that this issue isn't specific to our approach (although it is
clearly exaggerated) - any plugin that has a JS filename change or adds a
new JS file will be in the same boat - JS translations won't work for
people who upgrade - until the new pack is built and their WordPress
downloads it (maybe 24 hours at worst?).
A more complex/complete solution would be when a plugin is updated with
new JS strings/files, delay releasing on .org until the language packs
have been regenerated. This would solve for all cases automatically. Is
something like that even feasible?
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/6188#comment:6>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list