If I am following all this correctly, we have general agreement that Jenkins should stop bundling plugins all together, yeah? ...but some technical ifs and buts about upgrading (Jesse, Stephen, KK, and Tom can solve, but should not use "pinning" to do so)?
Then to the extent we do want people to start using Jenkins with *some* plugins (this might still be a bit contentious, maybe we do want to start with 0 plugins), we want to put the most minimal UI possible in the front of a Jenkins initial setup that lets users pick those plugins, yeah? ...just want to make sure I am on the same page as everyone. On Thursday, August 20, 2015 at 8:47:59 AM UTC-7, Tom Fennelly wrote: > > Gus Reiber is going to draw some screens for what a "Plugin Selection > Wizard" might look like, allowing us to have a conversation about that. > -- 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/dc5546de-3716-4222-a457-8195bb6bc6e0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
