/usrmove?

[Toshio Kuratomi]

On Wed, Feb 08, 2012 at 09:53:20AM -0800, Adam Williamson wrote:
> On Wed, 2012-02-08 at 08:11 -0600, Chris Adams wrote:
> > Once upon a time, Stijn Hoop <stijn at sandcat.nl> said:
> > > On Wed, 08 Feb 2012 06:37:33 +0100
> > > Kevin Kofler <kevin.kofler at chello.at> wrote:
> > > > Adam Williamson wrote:
> > > > > Note that this has not actually been implemented in anaconda yet,
> > > > > so if you do an anaconda upgrade at this time, it will explode
> > > > > horribly. The bug requesting this support be added to anaconda is
> > > > > http://bugzilla.redhat.com/show_bug.cgi?id=787893 .
> > > > 
> > > > It's totally unacceptable that this "feature" has been merged in this 
> > > > incomplete state. Working upgrades should have been a prerequisite
> > > > for merging it! Anaconda upgrades are even part of our release
> > >                                                          ^^^^^^^
> > > > criteria! This affects both the DVD upgrades and preupgrade, which
> > > > are the 2 upgrade methods Fedora claims to support.
> > > 
> > > I did not see a release yet, where did you find it?
> > 
> > He said "release criteria".  Included in that is the Feature Freeze
> > (which was yesterday for F17), which includes:
> > 
> >   Once the Feature Freeze milestone is reached, all new features for the
> >   release should be:
> >   - substantially complete and in a testable state
> > 
> > If the anaconda support for UsrMove is not merged (and maybe not even
> > written?), then why was an untestable and incomplete feature merged?
> 
> Well, it becomes a semantic argument. You can, after all, install with
> the /usr move in place, right now. You can upgrade from F16 with /usr
> move in place, if you follow the yum instructions. You can then test the
> *feature itself* perfectly well. Arguably, anaconda support for the
> feature is not part of the feature. You could go either way on this, but
> it's not an obviously wrong statement.
>
I think I would fall firmly on anaconda support being needed for the
feature.  It was one of the things that the FPC was counting on when it
approved it, for instance.  If anaconda support doesn't make it in, we
won't be able to release with UsrMove activated.

I note that, just like the rel-eng dependency, the anaconda dependency is
not noted on the feature page and the completion percentage on the feature
page is marked as 100%.  It seems that this feature has pointed us at a flaw
when it comes to figuring out what points of collaboration are needed,
keeping the feature page updated as new points of collaboration are
discovered to go with the new plan, and making the completion percentage
reliable.

I've added these points to the Fixing Features page:
https://fedoraproject.org/wiki/Fixing_features#Specific_examples_of_where_the_Feature_Process_failed

I'll have to think about what sort of practical solutions exist.

-Toshio
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20120208/e5983109/attachment.sig>