Sorry, I have missed my action item in this thread. I am really afraid of the "it will take 15 minutes to implement the specification" statement. Sure, it's just 15 minutes if we agree that approximately 5% of Jenkins installations get seriously impacted by the change and lose critical plugins without preliminary announcement. It is a big number of users whom we do not want to lose IMO. That's why I requested the rollout plan so that we are more careful with delivering the change.
Just to clarify the request, I would expect the following... 1. Do you plan to create a blogpost announcing the change in advance (e.g. 2 weeks before the plugins are removed)? 2. Would you add some administrative warnings directly to the Jenkins instances using plugins? Itcan be implemented via a security announcement with existing tools AFAICT 3. Do you plan to notify plugin maintainers in advance so that they have a chance to react before the plugins disappear from the main UC? 4. Do you plan to offer workarounds so that users can keep using the plugins for a while (e.g. by downloading from the experimental UC or so)? One may say that it is enough to just announce a change in the weekly changelog and then reference it in upgrade guidelines. I am not 100% sure about that, because, should a security release happen at the same timeframe, users may be dead in water if they depend on the main update centers (not recommended for paranoid setups, I'd guess). Once again, I totally support deprecating Ruby Runtime and I appreciate that you drive the effort. But we just need to be careful with that to avoid major breaking precedents. BR, Oleg On Sunday, July 1, 2018 at 12:52:46 PM UTC+2, Daniel Beck wrote: > > > > On 15. Jun 2018, at 01:08, Oleg Nenashev <[email protected] > <javascript:>> wrote: > > > > before the JEP is accepted, it would be great to see a rollout plan > which is currently missing in the JEP. > > > > I don't understand this request. > > It'll take me 15 minutes to implement the specification if I don't need to > wait for (with JEP fairly redundant) PR reviews. All actions listed are > very trivial, with the potential exception of identifying undoing > workarounds in core (and those can be done whenever we get around to them). > > -- 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/8f5a20c4-1443-46a3-bd41-2d0fdd17de61%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
