This is very helpful.
Thank you so much, Sumatra.

I will take a look and gradually join the activity.


On Thu, Nov 17, 2016 at 4:59 AM, Sumantro Mukherjee <> wrote:

----- Original Message -----
> From: "Yongsub Chung" <>
> To:
> Sent: Saturday, November 12, 2016 2:47:14 AM
> Subject: Introduction: Raymond Chung
> First of all,
> Thank you for making Fedora Linux great. And, I am sure the QA team's
> contribution is essential to keep Fedora in high quality distribution.
> My name is Raymond Chung, and I have been in the industry around 15 years,
> but I still feel that I don't know enough. I used Linux since I was in
> college. I started with RedHat 5.5. I used it through Fedora 3, and switched
> to Gentoo, and FreeBSD, and, Ubuntu, and settled back to Fedora since Fedora
> 17, (I guess).
> My best interest is Kernel testing. Whenever I run into a kernel issue, such
> as driver, or performance, I couldn't solve efficiently, or basically give
> up. I want to know more about kernel, and recently joining QA team might be
> a good way to get more experience with kernel.
> Outside of working with computer, I play music. I love rock music, but jazz
> and classical are my interests, too.
> Feel free to reach me.
> I am glad to be part of QA team.

Hey Ray

Sorry for the delayed response , as you might know we close to the release . You can start with Fedora QA by creating a FAS account! Once you are done with the basics you can start with  Release Validation testing. In Release Validation all you need to do is to check the nightly/TC/RC against certain criteria. For example, let's take the latest RC (Fedora 25 RC 1.3), you can run test cases which are mentioned [1] and submit your results in the test matrix.

Note that each of the test cases[2] will have "How to test" section which will have the steps (to be executed sequentially) and if the results match with the expected results you can mark it as pass by editing the wiki page {{result|PASS|<fas_username>}} . Always make sure to check for "Associated release criterion" which can be found on the top of test case page , if your test case fails you can mark it fail by editing the wiki page {{result|FAIL|<fas_username>}} and file a bug at RHBZ [3] under Fedora.

 You can always find the ‘current’ validation pages using these addresses:

You can also do update-testing, update testing is where a tester tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL. You can go to where you can sort the packages with Fedora Releases and tags viz "pending" & "testing" . You can read much about update testing here [4]. You can also, use fedora-easy-karma for giving out feedbacks.


Since you are specifically interested in Kernel , you can check [] and help us to test for each of these updates and modules.
test mailing list --
To unsubscribe send an email to