I've made this JEP-216 Draft so that it can be referenced in discussions and form the prototype, but as noted it needs quite a bit of work.
On Tuesday, August 28, 2018 at 7:01:57 AM UTC-7, Daniel Beck wrote: > > > > > On 28. Aug 2018, at 15:10, Oleg Nenashev <[email protected] > <javascript:>> wrote: > > > > I can imagine a local company which installs a single localization > plugin > > That's why I lean towards having separate plugins for each locale. > > … and an aggregator. It's free. Only needs updates whenever a locale > plugin is added or removed. I really don't understand the resistance here. > > > Depends on the installation logic implementation, but generally "yes". > > Which installation logic would you consider to be supported (i.e. we > wouldn't close a related Jira issue immediately) and does not install > whatever is available on your chosen update site? CLI command, UI, even > install-plugins.sh and configuration-as-code plugin install the newest > available release of dependencies. > > -- 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/8a4cc4fa-0eb6-43d3-8571-77b4dac2805c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
