I'm adding the fedora-devel-list as I think this should be discussed there. Andre Costa escribió: > Hi folks, > > bug #372011 [https://bugzilla.redhat.com/show_bug.cgi?id=372011] is > hosting a heated debate about anaconda & F8, how this dreadful bug has > been hurting F8 reputation and so on (I'm one of the poor souls that > have been affected by it -- and have been saved by patched .img > provided by Jeremy Katz > [http://katzj.fedorapeople.org/updates-f8-yumloop.img]). It has hurted very much I must say. > One thing that's clear is that anaconda QA missed some key spots, and > also that we (users) didn't help much on the process, allowing the bugs > to remain hidden until the version was officially released, which led to > a lot of stress among users and developers. The problem is that most users don't have time and resources to test twice a year a new release. 6 months for development+beta testing+RC testing is just too little. IMHO. Also, what kind of QA does Fedora have today? I'm not throwing mud at anyone, it's just that I don't have the slightest idea! (As Lucy used to say in the Peanuts Gang). There should be a list of things that have to be tested, and for each one of them, testers should report on the output of the test. Some items are more critical then others, and so should have more test reports. Just some ideas that just cracked out of my head. :-D > I would really like to participate more during the beta stage of new > Fedora versions. However, as I stated on Comment #97 > [https://bugzilla.redhat.com/show_bug.cgi?id=372011#c97] I can't really > install beta versions on my system at home, I use it daily, including > for work. This is exactly what I stated before: you don't have the resources. > But, AFAICS the other aspects of the installation process are pretty > much stable and independent from the current installation (language > selection, keyboard selection etc.), and the critical step for an > upgrade is dependency solving / package selection. > > So, what if the developers provided early access to this particular > part of anaconda only? I mean, in read-only mode, it would just gather > information about the packages currently installed and confirm if it > would be able to handle an upgrade on a "real" installation scenario? > It could for instance stop right after depsolve and show some > statistics. Well, nobody could ensure that the beta anaconda will not bite your disk. It is pre-beta. > Believe me, if I was sure that I could test anaconda in read-only mode I > would gladly do it, at any step before the official release. Chances > are that test coverage would improve considerably, and no installation > would be touched during this process. > > Does this make any sense to anyone? Would this help? Is it already > possible somehow? What I do see as something Fedora Project should do is whats commented in comment #104 [https://bugzilla.redhat.com/show_bug.cgi?id=372011#c104] about information on the web page of how to collaborate with the project. What would be a hugh plus for the project. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
