Should a working fedup in Fedora N's stable repository be a release criterion for N+1?

[Adam Williamson]

On Tue, 2013-12-17 at 15:16 -0800, Andrew Lutomirski wrote:
> I have a tendency to upgrade to a new Fedora release as soon as it's
> final, and I sometimes upgrade even sooner.  ISTM that the official
> upgrade process is almost always broken, often for known reasons.
> Should one of the criteria for releasing Fedora N+1 be that a
> fully-updated Fedora N must be able to successfully complete 'fedup'
> or whatever the current preferred upgrade program is?
> 
> (FWIW, the current bug is particularly nasty -- fedup 0.7.0 apparently
> can't actually update anything, and the sequence:
> 
>  - Install fedup 0.7.0
>  - Try it and watch it fail or hang
>  - Update to fedup 0.8.0 from updates-testing
>  - Run fedup
> 
> ends up downloading all rpms *twice* a sucking up a correspondingly
> immense amount of disk space.

Um, I'm fairly sure it doesn't. It only re-downloads stuff that's
different from the previous run.

We did test upgrades to F20 with 0.7, and they did work in testing, and
quite a lot of people reported success with fedup in the last two weeks
when at least some of them likely used 0.7.

You have to bear in mind it's release day today, and there's always
weirdness on release day, and people who have success generally don't
report it while those who hit failure almost always do. I've been
advising people to upgrade to 0.8 and retry just as a kind of generic
piece of advice; for many of them, it'd probably work if they just
retried with 0.7. 0.8 does fix several bugs compared to 0.7, but 0.7
wasn't entirely broken.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net