Release criterion proposal: upgrade methods

drago01 drago01 at gmail.com
Wed Sep 26 14:47:16 UTC 2012


On Wed, Sep 26, 2012 at 4:41 PM, Tim Flink <tflink at redhat.com> wrote:
> On Mon, 24 Sep 2012 10:32:01 -0600
> Tim Flink <tflink at redhat.com> wrote:
>
>> As currently written, the upgrade criterion in the Fedora 18 beta
>> release requirements [1] reads:
>>
>> The installer must be able to successfully complete an upgrade
>> installation from a clean, fully updated default installation (from
>> any official install medium) of the previous stable Fedora release,
>> either via preupgrade or by booting to the installer manually. The
>> upgraded system must meet all release criteria.
>
> Wow, I'm glad that I didn't just change the wiki without sending
> something out to test@ - I thought this was a minor, uncontroversial
> change ... I was wrong :)
>
> From the discussion in this thread, it sounds like we're proposing to
> change the one release criterion to two - one for beta, one for final.
>
> For beta:
>
> "It must be possible to successfully complete an upgrade from a fully
> updated installation of the previous stable Fedora release with the
> 'minimal' package set or the package set for a release-blocking desktop,
> using any officially recommended upgrade mechanism. The upgraded system
> must meet all release criteria."
>
> For final:
>
> "It must be possible to successfully complete an upgrade from a fully
> updated installation of the previous stable Fedora release with the
> 'minimal' package set or the package set for a release-blocking desktop,
> using all officially recommended upgrade mechanisms. The upgraded system
> must meet all release criteria."
>
> The implication being that at least one upgrade method has to work for
> beta and all have to work for final.
>
> Would we OK with shipping beta with only yum upgrades working? While
> it's not currently a 'recommended' method for upgrades right now as far
> as I know, that could certainly change.

No that way the upgrade method used by most users (which is even new
code this time) will get even less testing.


More information about the test mailing list