On Monday, August 17, 2015 at 9:11:25 PM UTC+1, Jesse Glick wrote: > > On Fri, Aug 14, 2015 at 5:51 PM, Kohsuke Kawaguchi <[email protected] > <javascript:>> wrote: > > when a plugin is split from core in version X, people upgrading > > from a version earlier will experiene functionality loss. > > Well I think this is what we should be spending a little effort > fixing. IMO there be *no* bundled plugins, so a new installation > (virgin `$JENKINS_HOME`) has no enabled plugins. The question is how > to deal with upgrades. >
I tried to distill my understanding of what Jesse described in a diagram ala ... <https://lh3.googleusercontent.com/-zdIH5jF9Itk/VdOKMhZLc9I/AAAAAAAABSg/lZ5Stsvug3g/s1600/Screenshot%2B2015-08-18%2B20.37.32.png> Obviously it's high level and doesn't go into detail on e.g. how a plugin selection wizard might actually work + doesn't detail how split plugins are actually resolved. -- 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/8934c392-a3a4-4c65-a316-3864188b32b0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
