On Fri, Jan 5, 2018, at 7:28 AM, Jan Kurik wrote: > Anaconda installer will be split into several modules that will > communicate over DBus using stable API. For the curious this blog entry is useful: http://blog-jkonecny.rhcloud.com/2017/06/16/shining-new-anaconda-modularisation/ I also would still like http://blog-jkonecny.rhcloud.com/2017/06/16/shining-new-anaconda-modularisation/#comment-3366641149 However my main concern here is: Anaconda is a baseline requirement for really doing much at all in releasing anything "Fedora" - for example we use Anaconda to generate both cloud images and the base container images. And obviously it's required to do bare metal installs. There are a few ways I could imagine doing this; ideally Fedora releng would have a real branching concept. I think it can sort of be set up manually. Do you have any plans to request that? At least let's be ready with a fallback plan of using the existing codebase? Are there going to be git branches upstream so fixes can still land in the current installer? For example I had plans to work on https://github.com/rhinstaller/anaconda/issues/1259 sometime soon, and *hopefully* it shouldn't conflict with modularization but it seems likely the change would need to go in both branches or so? _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
