On Mon, Jan 8, 2018 at 2:01 PM, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote: > On Mon, Jan 08, 2018 at 07:04:31AM -0500, Martin Kolman wrote: >> Yep - basically, there will be no "old" and "new, DBUS/modular" >> Anaconda, the plan is to turn the current Anaconda to the new one one >> step at a time. >> >> This should allow us to fix bugs as usual and handle any unforeseen >> modularization issues early on one-by-one as they show up. > > It sounds like there actually isn't a contingency plan as such. Do you > think that this could all be reverted on Final Freeze day if we would > decide it's not working out? If not, let's not call that a contingency. I would argue this isn't a "Self Contained Change" but a system wide one. If anaconda is broken we can't even compose so this should all be landed and complete by the time the system wide features need to be. > I'm not saying we shouldn't do this, but let's be honest with > ourselves. If the contingency plan is "None: we'll have to hold up the > release for fixes if it's not ready", the Change plan should say that. And we should be honest that the "Final Freeze day" is _WAY_ too late to be working out whether we should revert this or not! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
