test June 2011

test@lists.fedoraproject.org

88 participants
216 discussions

[Fedora QA] #192: Proposed Test Day - IPv6 - June 8, 2011 (Wednesday)
by fedora-badges 08 Dec '11

08 Dec '11

#192: Proposed Test Day - IPv6 - June 8, 2011 (Wednesday) ----------------------+----------------------------------------------------- Reporter: lwang | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 15 Component: Test Day | Version: Keywords: IPv6 | ----------------------+----------------------------------------------------- On Jun 8, 2011 - the World IPv6 Test Day, we like to host a fedora IPv6 test day as well to help our fedora users to test out Fedora15's readiness on IPv6. A description of the World IPv6 Day is here: http://isoc.org/wp/worldipv6day/ And the full fedora IPv6 Test Day project is described here: https://fedoraproject.org/wiki/QA/Test_Day:2011-06-08_IPv6 -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/192> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 13

[Fedora QA] #179: Proposed Test Day - general bootloader and dual-boot event
by fedora-badges 08 Dec '11

08 Dec '11

#179: Proposed Test Day - general bootloader and dual-boot event ----------------------+----------------------------------------------------- Reporter: jlaska | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 16 Component: Test Day | Version: Keywords: | ----------------------+----------------------------------------------------- Dlehman informed me of tentative plans to transition to grub2 in Fedora 16. Documentation and development hasn't finished yet, so things are still somewhat flexible. This ticket serves as a mental-note so we don't forget this when Fedora 16 test day planning starts. https://fedoraproject.org/wiki/Anaconda/Features/Grub2Migration -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/179> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 1

[Fedora QA] #198: Clarifying ways to verify updated and skipped bootloader
by fedora-badges 08 Dec '11

08 Dec '11

#198: Clarifying ways to verify updated and skipped bootloader -------------------------+-------------------------------------------------- Reporter: rhe | Owner: rhe Type: enhancement | Status: new Priority: major | Milestone: Fedora 16 Component: Wiki | Version: Keywords: | -------------------------+-------------------------------------------------- The installation matrix now contains the update bootloader and skip bootloader tests which need be updated to better detect whether the bootloader was skipped or updated. (This ticket is branched from [https://fedorahosted.org/fedora-qa/ticket/86 ticket#86]) -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/198> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #154: Tracker: critical path test case creation
by fedora-badges 08 Dec '11

08 Dec '11

#154: Tracker: critical path test case creation -------------------------+-------------------------------------------------- Reporter: adamwill | Owner: adamwill Type: enhancement | Status: new Priority: major | Milestone: Component: Wiki | Version: Keywords: | -------------------------+-------------------------------------------------- = problem = We need more specific per-package guidance for proven tester testing, to make sure the testing covers all the relevant critical path functionality of each package. = enhancement recommendation = We can create a group of test cases in the Wiki for each critical path package. Bodhi could integrate with this system and, in the future non- numeric karma system, provide checkboxes for each test case for packages which have test cases available. fedora-easy-karma could provide an interface to display and check off test cases from the Wiki. This ticket can serve as a tracker for this process, which will be ongoing. To start with I will file tickets for each package which has so far been identified (on test and devel mailing lists) as an obvious candidate for such test cases, with a note of what should be covered for each package. Those tickets will block this one. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/154> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

3 57

[Fedora QA] #80: Add dual-boot release criteria
by fedora-badges 08 Dec '11

08 Dec '11

#80: Add dual-boot release criteria ---------------------------+------------------------------------------------ Reporter: jlaska | Owner: Type: enhancement | Status: new Priority: major | Milestone: Fedora 14 Component: Wiki | Version: Keywords: retrospective | ---------------------------+------------------------------------------------ = problem = See [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=590661 RHBZ#590661 - GRUB bootloader should have a few seconds delay on a multi- boot setup] = analysis = Due to RHBZ #590661, the dual-boot experience was not well understood and tested for the final release. It was discovered late and unclear whether this behavior was critical to Fedora success. = enhancement recommendation = The user experience of dual-boot scenarios was not well understood, as a result RHBZ #590661 did not clearly impact the release criteria. Recommend reviewing and making adjustments to the release criteria for dual-boot expectations. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/80> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #93: Review options to reward key QA contributors
by fedora-badges 08 Dec '11

08 Dec '11

#93: Review options to reward key QA contributors ---------------------------+------------------------------------------------ Reporter: jlaska | Owner: jlaska Type: enhancement | Status: new Priority: major | Milestone: Fedora 14 Component: Wiki | Version: Keywords: retrospective | ---------------------------+------------------------------------------------ = problem = During Fedora 13, a small amount was available to reward several key QA contributors for their efforts. = analysis = If possible, I'd like to repeat this in Fedora 14. = enhancement recommendation = What's the best way to say thanks? 1. Request and secure QA budget to reward key contributors 2. Researching reward options (maxamillion has discussed t-shirt ideas with the design team) -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/93> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #89: Improve tracking blocker review status
by fedora-badges 08 Dec '11

08 Dec '11

#89: Improve tracking blocker review status ---------------------------+------------------------------------------------ Reporter: jlaska | Owner: poelstra Type: enhancement | Status: new Priority: major | Milestone: Fedora 14 Component: Wiki | Version: Keywords: retrospective | ---------------------------+------------------------------------------------ = problem = Several bugs were changed so they fell off the tracking lists for Fedora 13. For example... * [http://bugzilla.redhat.com/505189 505189 - Going back to repo UI screen and and modifying Installation Repo causes traceback] * [http://bugzilla.redhat.com/577803 577803 - Adding repository requiring network fails if network is down] = analysis = In F-13, a bugzilla keyword was used to denote blocker status. However, aside from reviewing bugzilla comments, there was no query-able method to determine whether a blocker request is open, approved or denied. This led to several Fedora 13 bugs that were 1) fixed in Rawhide, 2) Moved to MODIFIED or CLOSED and not included, but not included in Fedora 13 (e.g. RHBZ #505189 and RHBZ #577803). Not knowing which bugs were already reviewed, also introduced time wasted reviewing previously reviewed bugs during blocker review meetings. = enhancement recommendation = Recommend reviewing process changes to avoid the scenarios leading up to RHBZ #505189 and RHBZ #577803. Some options discussed so far include 1. Document usage of bugzilla flags (suggested by jkeating) to track blocker requests. This likely involves creating a ''bot'' to police the tags? 2. Hardening the current keyword-based mechanism. Additional discussion points include: 1. Document generating exception report and document action plan for CLOSED Blocker bugs that did not go through VERIFIED. 2. More frequent nag mails leading up to release milestones. Notification of NEW or ASSIGNED bugs goes to the maintainer, and MODIFIED bugs goes to QA. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/89> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 21

[Fedora QA] #149: Mentor Request
by fedora-badges 08 Dec '11

08 Dec '11

#149: Mentor Request -----------------------------------------+---------------------------------- Reporter: hellork | Owner: Type: proventester request | Status: new Priority: minor | Milestone: Component: Proventester Mentor Request | Version: Keywords: | -----------------------------------------+---------------------------------- = phenomenon = I am interested in joining the protesters and I'm requesting a mentor. = reason = I have been filing bug reports and working on submitting a couple new projects to Fedora. I have a good working knowledge of Yum update, C, C++, Makefiles, Bash, Python, Java, and RPM, packaging, etc. = recommendation = Sign me up! -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/149> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #196: proventester request
by fedora-badges 08 Dec '11

08 Dec '11

#196: proventester request -----------------------------------------+---------------------------------- Reporter: azur3l1ght | Owner: Type: proventester request | Status: new Priority: major | Milestone: Component: Proventester Mentor Request | Version: Keywords: | -----------------------------------------+---------------------------------- Hi , i would like to apply for proven testers team. I have 4 years as QA in different projects and recently switched to Fedora . Greetings Georgi -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/196> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #189: I would like to join the proven testers and would like to have a mentor
by fedora-badges 08 Dec '11

08 Dec '11

#189: I would like to join the proven testers and would like to have a mentor -----------------------------------------+---------------------------------- Reporter: ikatalinikov | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Proventester Mentor Request | Version: Keywords: | -----------------------------------------+---------------------------------- = bug description = = bug analysis = = fix recommendation = -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/189> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 5

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 2011