#70: proventesters request - tomspur -----------------------------------------+---------------------------------- Reporter: tomspur | Owner: Type: proventester request | Status: new Priority: major | Milestone: Component: Proventester Mentor Request | Version: Keywords: | -----------------------------------------+---------------------------------- = Full Name = [https://fedoraproject.org/wiki/User:Tomspur Thomas Spura]
= Experience = * Currently, I maintain 18 packages in fedora [1], also quite important ones like python3 and ipython. I'm also provenpackager, so I know how to break things from a packager view of point ;)
* I've already given much feedback in bodi (I'm most of the time in the top 8 in [2]).
- prevented a broken evolution package getting in: http://admin.fedoraproject.org/updates/evolution-2.30.1-3.fc13
- my karma would make 'proxy karma' unnecessary, e.g.: https://admin.fedoraproject.org/updates/xorg-x11-drv-ati-6.13.0-1.fc13
* Most of the time, I'm running XFCE (and just sometimes GNOME) and because most other QA members are constantly running GNOME, the XFCE packages are unlikely to get tested. So I would primary focus on testing XFCE packages.
Further links can be found at [https://fedoraproject.org/wiki/User:Tomspur my usersite].
[1] https://admin.fedoraproject.org/pkgdb/users/packages/tomspur [2] https://admin.fedoraproject.org/updates/metrics/?release=F13
= Summary =
I believe, I've already shown some of the capabilities, that are needed to get proventester, know how updates are working and know how to break something as a packager and therefore what to check as a QA member...
So I don't need much guidence to finish the proventesters process and here I'm requesting a mentor.
#70: proventesters request - tomspur ------------------------------------------+--------------------------------- Reporter: tomspur | Owner: Type: proventester request | Status: new Priority: major | Milestone: Component: Proventester Mentor Request | Version: Resolution: | Keywords: ------------------------------------------+--------------------------------- Comment (by jlaska):
Wow Thomas, great request and application to join the group! The information provided clearly demonstrates your skills.
We are continuing to define the proventester process. I will leave your ticket open until someone from the QA team can act on the request and provide test guidance. Stay tuned, and feel free to take part in the discussion at test@lists.fedoraproject.org
#70: proventesters request - tomspur ------------------------------------------+--------------------------------- Reporter: tomspur | Owner: jlaska Type: proventester request | Status: assigned Priority: major | Milestone: Component: Proventester Mentor Request | Version: Resolution: | Keywords: ------------------------------------------+--------------------------------- Changes (by jlaska):
* owner: => jlaska * status: new => assigned
Comment:
Greetings Thomas,
I'll be happy to sponsor you into the proventesters group. Please take a moment to read through the [https://fedoraproject.org/wiki/Proven_tester proventester instructions]. As a proventester, our job isn't to exhaustively find all defects in a software update. The focus is to determine whether the proposed software update negatively impacts core system functionality. Pay particular attention to the documented feedback procedures.
Once you have read the instructions, please confirm that you ... 1. have read and understand the instructions, and intend to follow the instructions when testing Fedora critical path updates 2. understand how to enable the update-testing repository 3. are familiar with providing test feedback using either the [http://bodhi.fedoraproject.org/ Bodhi web interface], or the [https://fedoraproject.org/wiki/Fedora_Easy_Karma fedora-easy-karma utility]
Based on [http://lists.fedoraproject.org/pipermail/devel/2010-June/137413.html recently published bodhi statistics], it seems you have an understanding of points #2 and #3 above. Please let me know if you have any questions or concerns. Once I hear back, I'll sponsor your membership in the proventesters group.
#70: proventesters request - tomspur ------------------------------------------+--------------------------------- Reporter: tomspur | Owner: jlaska Type: proventester request | Status: assigned Priority: major | Milestone: Component: Proventester Mentor Request | Version: Resolution: | Keywords: ------------------------------------------+--------------------------------- Comment (by tomspur):
Hi James,
thanks for sponsoring me. :) I've read the proventester instructions, and have been following them (more or less) with all my karma, I posted till now. The only difference was, that when in doubt, I didn't give any karma and not a neutral feedback like suggested in 'Unfamiliar packages'. But surely, neutral feedback is better than none at all...
(Besides that, as you pointed out, I understand points #2 and #3 as well.)
My only question for now is, for how many releases will the critpath be enabled? Are there enought testers for more than one release? (I'll be mostly testing F-13 right now.)
#70: proventesters request - tomspur ------------------------------------------+--------------------------------- Reporter: tomspur | Owner: jlaska Type: proventester request | Status: assigned Priority: major | Milestone: Component: Proventester Mentor Request | Version: Resolution: | Keywords: ------------------------------------------+--------------------------------- Comment (by jlaska):
Replying to [comment:3 tomspur]:
My only question for now is, for how many releases will the critpath be
enabled?
Are there enought testers for more than one release? (I'll be mostly testing F-13 right now.)
Thanks Thomas. Great question, I believe the Fedora updates system (bodhi) is setup to require proventester feedback for critpath packages in all releases. However, I'm confirming with lmacken to be sure.
Please apply to the 'proventesters' group in FAS. I will then sponsor your membership. Thanks!
#70: proventesters request - tomspur ------------------------------------------+--------------------------------- Reporter: tomspur | Owner: jlaska Type: proventester request | Status: closed Priority: major | Milestone: Component: Proventester Mentor Request | Version: Resolution: fixed | Keywords: ------------------------------------------+--------------------------------- Changes (by jlaska):
* status: assigned => closed * resolution: => fixed
Comment:
Replying to [comment:4 jlaska]:
Please apply to the 'proventesters' group in FAS. I will then sponsor
your membership. Thanks!
I see you have already applied. I have sponsored your request. Welcome to proventesters. Happy testing!
#70: proventesters request - tomspur ------------------------------------------+--------------------------------- Reporter: tomspur | Owner: jlaska Type: proventester request | Status: closed Priority: major | Milestone: Component: Proventester Mentor Request | Version: Resolution: fixed | Keywords: ------------------------------------------+--------------------------------- Comment (by lmacken):
Replying to [comment:4 jlaska]:
Thanks Thomas. Great question, I believe the Fedora updates system
(bodhi) is setup to require proventester feedback for critpath packages in all releases. However, I'm confirming with lmacken to be sure.
Yes, bodhi currently requires proventester feedback for critical path updates across all releases in bodhi.
-
fedora-badges