Ticket #70 (closed proventester request: fixed)

Opened 4 years ago

Last modified 4 years ago

proventesters request - tomspur

Reported by: tomspur Owned by: jlaska
Priority: major Milestone:
Component: Proventester Mentor Request Version:
Keywords: Cc:
Blocked By: Blocking:

Description

Full Name

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]).
  • 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 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.

Change History

comment:1 Changed 4 years ago 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@…

comment:2 Changed 4 years ago by jlaska

  • Owner set to jlaska
  • Status changed from new to assigned

Greetings Thomas,

I'll be happy to sponsor you into the proventesters group. Please take a moment to read through the 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 Bodhi web interface, or the fedora-easy-karma utility

Based on 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.

comment:3 follow-up: ↓ 4 Changed 4 years ago 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.)

comment:4 in reply to: ↑ 3 ; follow-ups: ↓ 5 ↓ 6 Changed 4 years ago by jlaska

Replying to 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!

comment:5 in reply to: ↑ 4 Changed 4 years ago by jlaska

  • Status changed from assigned to closed
  • Resolution set to fixed

Replying to 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!

comment:6 in reply to: ↑ 4 Changed 4 years ago by lmacken

Replying to 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.

Note: See TracTickets for help on using tickets.