test June 2010

test@lists.fedoraproject.org

81 participants
215 discussions

[Fedora QA] #78: Request for Mentor
by fedora-badges 07 Jul '10

07 Jul '10

#78: Request for Mentor -----------------------------------------+---------------------------------- Reporter: robatino | Owner: Type: proventester request | Status: new Priority: major | Milestone: Component: Proventester Mentor Request | Version: Keywords: | -----------------------------------------+---------------------------------- I am requesting a Mentor as described in [https://fedoraproject.org/wiki/QA/JoinProvenTesters]. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/78> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 4

[Fedora QA] #69: Proventester mentor request
by fedora-badges 07 Jul '10

07 Jul '10

#69: Proventester mentor request -----------------------------------------+---------------------------------- Reporter: mcloaked | Owner: Type: proventester request | Status: new Priority: major | Milestone: Component: Proventester Mentor Request | Version: Keywords: | -----------------------------------------+---------------------------------- I am requesting a mentor to guide me in order to become a proventester for Fedora QA As described in https://fedoraproject.org/wiki/QA/JoinProvenTesters:Draft, I need a mentor to guide me. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/69> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 4

[Fedora QA] #64: Mentor request for proventesters
by fedora-badges 07 Jul '10

07 Jul '10

#64: Mentor request for proventesters ---------------------+------------------------------------------------------ Reporter: schaiba | Owner: Type: task | Status: new Priority: major | Milestone: Component: Trac | Version: Keywords: | ---------------------+------------------------------------------------------ -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/64> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 4

[Fedora QA] #67: Request for Mentor
by fedora-badges 07 Jul '10

07 Jul '10

#67: Request for Mentor -----------------------------------------+---------------------------------- Reporter: kparnell | Owner: Type: proventester request | Status: new Priority: major | Milestone: Component: Proventester Mentor Request | Version: Keywords: | -----------------------------------------+---------------------------------- As described in: http://fedoraproject.org/wiki/QA/JoinProvenTesters:Draft I am requesting a mentor to guide me. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/67> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 6

[Fedora QA] #70: proventesters request - tomspur
by fedora-badges 07 Jul '10

07 Jul '10

#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. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/70> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 6

[Fedora QA] #71: Proventester request
by fedora-badges 06 Jul '10

06 Jul '10

#71: Proventester request -----------------------------------------+---------------------------------- Reporter: kevin | Owner: Type: proventester request | Status: new Priority: major | Milestone: Component: Proventester Mentor Request | Version: Keywords: | -----------------------------------------+---------------------------------- I've been working with Fedora for a while and would like to be a proventester so I could help test Xfce and other updates in the critical path. Happy to work with a mentor or whatever. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/71> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 7

[Fedora QA] #74: Proventester Mentor Request
by fedora-badges 03 Jul '10

03 Jul '10

#74: Proventester Mentor Request -----------------------------------------+---------------------------------- Reporter: tk009 | Owner: Type: proventester request | Status: new Priority: minor | Milestone: Component: Proventester Mentor Request | Version: Keywords: | -----------------------------------------+---------------------------------- Looking for a mentor type brother/sister. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/74> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 2

Re: Proven Tester documentation
by John Dulaney 01 Jul '10

01 Jul '10

It is done:https://fedoraproject.org/wiki/User:Jdulaney From: awilliam(a)redhat.com To: test(a)lists.fedoraproject.org Date: Mon, 28 Jun 2010 15:35:57 -0700 Subject: Re: Proven Tester documentation On Mon, 2010-06-28 at 18:12 -0400, John Dulaney wrote: > During the meeting today it was decided to combine the Proven Tester > and Join Proven Tester documentation. I haven't changed much: Well, more we asked you to provide a draft of a combined page, so we could see whether it looks better than way :) It's difficult to get a feel for the draft from a mailing list transcription. Could you please instead create it as a new draft page in your own personal space on the Wiki, so we can see it in the proper Wiki layout? Your personal space is under your FAS username - so mine's at https://fedoraproject.org/wiki/User:Adamwill . You can create new pages under this, like I put my first draft of the proven testers page at https://fedoraproject.org/wiki/User:Adamwill/Draft_proventesters_instructio… . You can create a similar page name under your space for your draft. Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net _________________________________________________________________ The New Busy is not the old busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:…

3 3

Proposed release criteria additions for F14+
by Adam Williamson 30 Jun '10

30 Jun '10

Sorry for the cross-post, but figured it's worth CCing devel in case anyone has concerns on these. I'm currently working on a plan to expand desktop validation testing. As part of the discussion around this, Christoph Wickert proposed several additions to the release criteria that seem sensible to me. I'd like to propose we add these to the criteria for F14 and on: * Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring, must work * The desktop default update manager must not periodically check for updates when the system is booted live, but must periodically check for updates when running on an installed system * The desktop's offered mechanisms for shutting down, logging out and rebooting must work Anyone have comments or objections to these? Suggestions for what release they should come in? I'd say #1 should be final and #2 and #3 should be beta, off the top of my head. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net

5 8

Proven testers: mentoring
by Adam Williamson 30 Jun '10

30 Jun '10

So, we need to move fast with proven testers, as I said last night :) Given that, here's a quick off-the-top-of-my-head set of suggestions for proven tester mentoring. I'm not trying to hijack this process or anything, I just want to get something out there so we can get started and make sure we're able to accept the applications we have right now so we can get people out there testing. We obviously don't have instructions for the mentoring process yet, and it'd help to have some. I'll try and draft a wiki page for this soon, which Aaron will inevitably make much better. =) In the mean time, here's some quick thoughts. We have 14 open proventester requests. Easiest way to see them all is from this trac report: https://fedorahosted.org/fedora-qa/report/9 all the tickets under 'Proventester Mentor Request Release'. We should aim to accept these ASAP. Those of us who are already proventester members - see https://admin.fedoraproject.org/accounts/group/members/proventesters - should try and grab two or three of these requests each. We should then point our...mentor-ees?...to the proven tester instructions page: https://fedoraproject.org/wiki/Proven_tester and ask them to confirm that they've read the instructions, and that they're familiar with the process of enabling updates-testing and using the web interface or fedora-easy-karma to post feedback on updates. Then we should ask them to apply to the proventesters FAS group, and then sponsor them into the group. Ask them to let you know when they've filed their first batch of update feedback, and quickly look over it to make sure it looks in line with what we're aiming for. This is all coming off the top of my head, as I said, but I think it should be enough to get us going. Please do raise any suggestions, improvements, or anything I left out in my process. If anyone would like to go ahead and draft a mentor instructions Wiki page before I can (I've got to write the FWN QA beat next), please do! Alright, I'm off to pick a group of mentor-ees :) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net

3 5

← Newer
1
2
3
4
5
6
7
8
...
22
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test June 2010