Upcoming Test Days: Preupgrade and Xfce!


I was reminded of this today (I’d totally forgot) so in an effort to get this info out asap I’m gonna blockquote Adam’s blogpost 🙂

So this week we round out the Fedora 13 Test Day schedule, which has seen us run the gauntlet from NFS, through color management and SSSD, scale the heights of Graphics Test Week, and will see us come to a triumphant finish with the Preupgrade Test Day on Thursday 2010-04-29 and the Xfce Test Day on Friday 2010-04-30.

These are two juicy topics: preupgrade is the recommended method for upgrading from one Fedora release to the next, and is widely used. We also really need to have it working properly at release time, so we need your help to test and make sure it is! Xfce is one of the most popular ‘alternate’ Linux desktops, and has a very dedicated Fedora SIG which works hard to provide a smooth experience and live spin, and has organized the Test Day to make sure the Fedora 13 Xfce experience is second to none. So please come out and help us polish off these final Fedora 13 features!

As always, the Test Days will run all day in the #fedora-test-day channel on Freenode IRC. If you’re not sure about IRC, read the guide or use WebIRC. If you can’t do the testing on the Test Day, you can still run through the tests and provide your results earlier or later; you’ll just miss out on the real-time IRC discussion, but that’s okay. You can do the Xfce testing with a live image which will be provided on the Test Day page. Obviously this isn’t possible for the preupgrade testing, but you can test it in a virtual machine if you don’t want to (or can’t) mess with your real Fedora installation.

Testing is easy and there’s lots of guidance on how to do the testing and file your results on the Wiki pages – you don’t need any special skills to help out! Even if you get stuck, there will be QA team members, developers, and other testers on IRC to help you out. The more testing we get done the more polished Fedora 13 will be for everyone.

Out of Flamewar arises a Phoenix of Hope


I don’t remember the original post that got this whole thing going but in about 24 hours something awesome happened. The Fedora Project has set a goal turning users into contributors. If you have ANY free time and (just about) ANY skill we can find a place for you. One place where people are needed badly is testing. There are just more packages than there are testers, that’s just the way it is. There are only two ways to slove this 1. stop maintaining so many packages. If you cant find people to test it then its obvious no one uses it. This is the wrong answer. or 2. find more testers, this is the right answer. Spot came up with a great idea

… I posit an alternative suggestion:

* At firstboot, the installing user is asked if they would be willing to
participate in user-driven updates testing. It is explained to them that
in Fedora, updates to packages need to be tested by users, and that if
they opt-in, they will be prompted from PackageKit about updates which
need user testing. They can choose an update which needs testing from a
list. Once an update is selected from the list, PackageKit will apply
the update from updates-testing, then open a new window which contains:

* General update testing advice
* Package specific update testing advice (this can live on the wiki)
* A graphical selector for giving +1 (works great!), 0 (cannot determine
state) or -1 (something didn’t work)
* A text box for inputting comments

The user then submits the results, which go into Bodhi. Once results are
submitted, that update no longer appears in the PackageKit “updates
which need testing” list.

If they report a 0 or -1, they are then prompted to back out the update
by PackageKit (at their choice).

* On the backend, should a user choose to opt-in, they would be prompted
to create a FAS account (or authenticate to an existing FAS account)
(e.g. RHN handling in the past). They would _NOT_ be required to sign
the Fedora CLA in order to participate in user-driven testing, as
reported results from QA testing has already been determined to be
non-copyrightable and thus, not considered a contribution.

Each user who opts-in to perform user-driven testing will have it
flagged in their account. Each successful update testing submission will
be minimally logged (package, target, timedate stamp) and a count
incremented for unique update feedback performed.

In thanks for their testing, users will be informed (at firstboot) that
they will receive Fedora swag, both in random drawings and at certain
threshold points (give good feedback on N updates and get a Fedora
Tester T-shirt).

Users can choose to opt out at any time. …

But that wasn’t the only proposed solution. There are some that think that poping crap up at people on first boot is bad form and that we should strive to give people a running functional desktop before we start bothering them. Meh good point. So here was another solution This
one by Mike McGrath.

Random thought: We could put a pretty ajaxy signup thing on
start.fedoraproject.org that keeps them logged in via community.

I’m thinking of something similar to how google.com works now. With no
login you get the generic pageg. With a login you might get a more
feature rich “targeting contributors” page. If they’ve gone far enough to
do the ajax sign up, we can try to consider them a potential contributor.

This topic is still hot on the Advisory Board Mailinglist , but what are your thoughts? Would you test packages for swag? Would you test packages if there was no swag? Would you be annoyed if this was presented to you at firstboot? Let me know in the comments or link me if you put your thoughts up somewhere eles.