> On 28. Aug 2018, at 14:54, Oleg Nenashev <[email protected]> wrote:
>
> I do not know any organization which actually does that. Usually Jenkins is
> managed via various shared services teams if it gets to such scale, and
> having different localizations makes the system generally unsupportable.
> Imagine you get a support tickets with screenshots in Russian.. oh wait, it
> happens in JIRA sometimes.
So they would simply not install any localization plugin. Great, so they're
completely irrelevant as far as considering their preferences goes (beyond
removing translations from everywhere else).
> I do not see a particular need in an aggregator plugin, especially taking our
> experience with maintaining them. For example, the current version of
> Pipeline aggregator just contains obsolete plugins with known
> incompatibilities like JEP-200.
Aggregator plugins do not 'contain' anything, they just list a bunch of
plugins. If you install them, you get the newest releases of dependencies
anyway, unless you do something unsupported with the metadata.
--
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/F5F32EE4-66F0-4892-B7CA-50CB386D8318%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
