Re: Upgrade to F30 gone wrong

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Roberto Ragusa <mail@xxxxxxxxxxxxxxxx> igorleak hau idatzi zuen (2019 mai. 6, al. 15:34):
On 5/6/19 1:40 PM, Julen Landa Alustiza wrote:

> We found this bug before releasing, but it is not a release blocking bug (the upgrade criteria just cover clean n and n-1 upgrading to n+1 and this bug just happens whith continously upgraded systems since fc21 or lower)

Wait a moment, is n and n-1 defined to "installed from scratch n and n-1?".
Is this a precedent that n-installed is different than n-through-upgrades?

Regards.

--
    Roberto Ragusa    mail at robertoragusa.it

Technically speaking and for our releasing criteria yep, we block on fresh fc28/fc29 default installation of blocker package sets upgrades to fc30, previously upgraded fc28/fc29 are out of scope.

We do our best to support upgrading from previously upgraded systems, but they're not considered blocker bugs if clean default installations of n or n-1 are not affected

https://fedoraproject.org/wiki/Fedora_30_Beta_Release_Criteria#Upgrade_requirements


_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux