On Thu, Nov 22, 2018 at 11:00 AM Kamil Paral <kparal@xxxxxxxxxx> wrote: ... > b) don't use testing updates at all during the whole cycle > > This makes the install process more stable (testing updates can't break it). The installed packages more closely match what the composes consist of (the composes never use testing updates, but occasionally they might include a few extra packages on top of what is currently stable, if QA requests it). After Beta, you will not end up with a system that contains testing packages, but the testing repo is disabled (that might throw some people off, if they don't know they should use dnf distrosync instead of dnf update). > The downside is that before Beta, you'll need to install the system and then also update it, to have all the latest packages (including testing updates). > This one has my vote, as I really feel that having install media that is unpredictably reliable (especially at Beta) reduces our ability to get people testing it. _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-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/test@xxxxxxxxxxxxxxxxxxxxxxx
