test-announce January 2011

test-announce@lists.fedoraproject.org

4 participants
6 discussions

Re: [Test-Announce] Fedora Rawhide Test Day for Network Device Naming on January 27th 2011
by Narendra_K＠Dell.com 27 Jan '11

27 Jan '11

On Wed, Jan 19, 2011 at 10:30:27PM +0530, K, Narendra wrote: > Hello, > > We are conducting a Fedora Rawhide Test Day on "Network Device Naming" on Thursday, January 27th 2011. > > The objective is to test the new naming scheme for onboard and PCI add-in network interfaces as suggested by 'biosdevname' utility. It would be great if you could participate and provide your feedback which would help us flush bugs. > > Please join us on IRC for the event on freenode in #fedora-test-day all day on January 27th 2011. > > https://fedorahosted.org/fedora-qa/ticket/159 > https://fedoraproject.org/wiki/Test_Day:2011-01-27_Network_Device_Naming_Wi… Hello, The test day is in progress. Your participation and feedback would be greatly appreciated. With regards, Narendra K

1 0

Announcing 389 Directory Server 1.2.8 Alpha 1 for testing
by Rich Megginson 25 Jan '11

25 Jan '11

The 389 team is pleased to announce the availability for testing of Alpha 1 of version 1.2.8. This release contains many bug fixes. On those platforms which have OpenLDAP built with Mozilla NSS crypto support (Fedora 14 and later), the packages are built with OpenLDAP instead of the Mozilla LDAP C SDK. WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882 To fix, run this: fixfiles -R 389-ds-base restore If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6 or 1.2.7, there is no problem. WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See http://port389.org/wiki/Subtree_Rename#warning:_upgrade_from_389_v1.2.6_.28… for more information. If you are upgrading from 1.2.5 or earlier, or a 1.2.6 or 1.2.7 stable release, there is no problem. The new packages and versions are: * 389-ds-base 1.2.8.a1 ***We need your help! Please help us test this software.*** It is an Alpha release, so it may have a few glitches, but it has been tested for regressions and for new feature bugs. The Fedora system requires that packages go into Testing until verified and pushed to Stable. The more testing we get, the faster we can release these packages to Stable. See the Release Notes for information about how to provide testing feedback (or just send an email to 389-users(a)lists.fedoraproject.org). === Installation === yum install --enablerepo=[updates-testing|epel-testing] 389-ds setup-ds-admin.pl === Upgrade === yum upgrade --enablerepo=[updates-testing|epel-testing] 389-ds-base setup-ds-admin.pl -u === Bugs Fixed === This release contains many bug fixes. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing. * Bug List for 389 1.2.8 https://bugzilla.redhat.com/showdependencytree.cgi?id=656390&hide_resolved=0 * Release Notes - http://port389.org/wiki/Release_Notes * Install_Guide - http://port389.org/wiki/Install_Guide * Download - http://port389.org/wiki/Download

1 0

Fedora Rawhide Test Day for Network Device Naming on January 27th 2011
by Narendra_K＠Dell.com 21 Jan '11

21 Jan '11

Hello, [It looks like my earlier post did not hit the list, so making this post again] We are conducting a Fedora Rawhide Test Day on "Network Device Naming" on Thursday, January 27th 2011. The objective is to test the new naming scheme for onboard and PCI add-in network interfaces as suggested by 'biosdevname' utility. It would be great if you could participate and provide your feedback which would help us flush bugs. Please join us on IRC for the event on freenode in #fedora-test-day all day on January 27th 2011. https://fedorahosted.org/fedora-qa/ticket/159 https://fedoraproject.org/wiki/Test_Day:2011-01-27_Network_Device_Naming_Wi… With regards, Narendra K

1 0

Call for reviewing TCMS use cases and comparison!
by He Rui 18 Jan '11

18 Jan '11

Greetings! Wiki workflow/use cases are reorganized and grouped by general and main test events(runs) use cases. The general cases cover the basic uses of wiki, and the events cases covers the detailed certain steps for organizing the events. Please review it: https://fedoraproject.org/wiki/Rhe/tcms_use_cases Meanwhile, Wiki and Nitrate comparison is also listed and grouped by above use cases. I've listed as many features as I can think out for comparison. Please have a look and see if any features are missed. You can review it by the use case you're familiar with if reviewing all of them is tough, but be aware that features compared in former use cases are not listed in later cases again to avoid overlaps: https://fedoraproject.org/wiki/Rhe/tcms_Comparison Ticket#152[1] is currently set up for tracking this event. Feel free to add comments or discuss it here. Note: the feedback deadline is Jan 21, the end of this week. After that date, I'll move forward to the next phase. Waiting for your feedback! Cheers, Hurry [1] https://fedorahosted.org/fedora-qa/ticket/152 -- Contacts Hurry FAS Name: Rhe Timezone: UTC+8 TEL: 86-010-62608141 IRC nick: rhe #fedora-qa #fedora-zh

1 0

quick reminder: bugzappers meeting today
by Adam Williamson 11 Jan '11

11 Jan '11

A quick reminder that we have a Bugzappers meeting scheduled for today at 2100 UTC (that's 3hrs 20mins from now). Sorry, I don't have an agenda right now, someone else may supply one. I may only be partially present as I'm going out tonight. thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net

1 0

New test case and package test plan creation SOPs in production: call for test cases!
by Adam Williamson 11 Jan '11

11 Jan '11

Hi, everyone. Thanks to everyone who sent feedback on the drafts for the test case and package test plan creation SOPs. I have now put these SOPs into production, at the following addresses: https://fedoraproject.org/wiki/QA:SOP_test_case_creation https://fedoraproject.org/wiki/QA:SOP_package_test_plan_creation I have created links to them from other places in the QA wiki space. It would be nice to have them called out from within the developers/package maintainers space, but I'm not sure where would be appropriate: does anyone have suggestions? Now these are in production, it would be great if people could start contributing test cases for packages, particularly test cases covering critical path functions. If you maintain a critical path package, please take a look at these two SOPs, and consider contributing test cases covering at least the critical path functionality of your package; this would help us greatly, and contribute to the improvement of critical path testing by the proven testers. For the QA group, please also consider contributing critical path test cases - you don't have to be a maintainer of a package to do it! If you know how to test the critical path functionality of a given package, please read the SOPs, write up test case(s) to do it, and categorize them appropriately. Thanks a lot! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

test-announce January 2011