Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))
tmraz at redhat.com
Wed Oct 31 14:33:33 UTC 2012
On Wed, 2012-10-31 at 16:12 +0200, Panu Matilainen wrote:
> On 10/30/2012 08:45 PM, Adam Williamson wrote:
> > On Tue, 2012-10-30 at 19:32 +0100, Gianluca Sforna wrote:
> >> I don't know if it's impossible to revert to the F17 anaconda at this
> >> time, however it is clear that F18 is going to be the longest release
> >> cycle we had in 9 years and somehow we need to avoid this in the
> >> future.
> > It's not impossible, well, nothing is impossible, but at this point it's
> > almost certainly more of a disruption than just plowing on with newui.
> > It's worth noting quite a lot of the early issues in this cycle -
> > particularly during Alpha - weren't actually much to do with newui; they
> > were more to do with changes in dracut which affected anaconda. oldui
> > wasn't fixed for that, so if were to try and switch back to oldui at
> > this point, we'd have to go through the whole process of adjusting the
> > code for the changes to dracut again, quite apart from any other issues.
> Makes me wonder... were the anaconda developers and FESCo aware of the
> oncoming major changes to dracut? At least I failed to see anything
> obviously related to that on a quick skim through the f18 feature list.
Good point, unfortunately there is no _actively enforced_ requirement to
have a Fedora Feature for every major changes in core components of
Fedora that affect other components.
No matter how far down the wrong road you've gone, turn back.
More information about the devel