> On 28. Aug 2018, at 08:44, Oleg Nenashev <[email protected]> wrote:
>
> I would rather prefer separate plugins for each localization.
> It would allow to properly form reviewer teams and to manage release cycles
> independently.
Only with an aggregator plugin. Otherwise the benefits of managing separate
per-language translation plugins are outweighed by the downsides on the user
side: In language diverse communities or organizations, having to install (or
request installation) of a new translation plugin every month, because now a
French/German/Italian/Russian/Portuguese/Spanish/Chinese/Turkish/Polish/Czech/…
speaking person wants their Jenkins localized in their own language seems
cumbersome.
Right now, it seems the best we can do is:
(Aggregator) -- depends on all --> (individual language plugins) -- each
depends on the --> (translation enablement plugin)
Or just put everything in one plugin because otherwise it becomes an
unmanageable mess. We can always split them like this if the one plugin becomes
unmanageable.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/F6CDB192-8732-4FEE-87E8-F7FE281A7646%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
