#1214 Change / reinterpret beta release criteria to test *stable* versions of previous releases
Closed None Opened 10 years ago by amluto.

= phenomenon =

There's a tendency for users who run {{{yum upgrade; fedup --source network <version>}}} to experience number of problems, especially if those users try to upgrade shortly after a new Fedora release becomes final. Often these problems were known before the release.

As a recent example, see [https://bugzilla.redhat.com/show_bug.cgi?id=1044086 Fedora bug #1044086].

= background analysis =

The current [https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F recommended way to upgrade to a new Fedora release] is:

Be sure to get the latest release, this may involve enabling updates-testing (yum --enablerepo=updates-testing install fedup in the command line).

This advice seems to have propagated to the [https://fedoraproject.org/wiki/QA:Testcase_upgrade_fedup_cli_previous_desktop QA testcases], which say:

Install fedup. It is usually a good idea to install the very latest version from updates-testing: su -c 'yum --enablerepo=updates-testing install fedup'

This seems to be in conflict with the Beta release criteria, which state:

For each one of the release-blocking package sets, it must be possible to successfully complete an upgrade from a ''fully updated installation'' of the previous stable Fedora release with that package set installed. [emphasis added]

The criterion wants a fully updated installation to be able to update, but the QA testcase tests something even newer than a fully updated installation.

= implementation recommendation =

I propose that the testcases change to say something like:

Install fedup. The stable version of fedup must be tested; fedup packages in updates-testing are out of scope for this test.

In addition, it may be worthwhile to change the advice on the [https://fedoraproject.org/wiki/FedUp FedUp wiki page] to delete the suggestion to use fedup from updates-testing.

It may also be worthwhile to consider all fedup packages in earlier versions of Fedora to be frozen as if they were part of an upcoming release during the beta and final freezes.


Why is this being filed as a fesco ticket? It's nothing to do with fesco.

I've already been working on rationalizing all this stuff over the last day. I don't think anything is needed from fesco.

It was suggested on the devel list. If there's a more appropriate forum, I'd be happy to move it. If you're planning on fixing it yourself, that's fine with me, too.

Closing for now, since it seems like fesco doesn't have to do anything here.

Login to comment on this ticket.

Metadata