test-announce July 2010

test-announce@lists.fedoraproject.org

4 participants
5 discussions

Proven Testers: now working on Fedora 14
by Adam Williamson 31 Jul '10

31 Jul '10

Hi, everyone. Just a heads-up to proven testers: now Fedora 14 has been branched, the proven tester process is in effect for Fedora 14 packages. Just like Fedora 13, critical path updates for Fedora 14 (even while it's in development) will require +1 from a proven tester and +1 from someone different. So, we really need proven testers to start testing those F14 packages! If you have a spare system you can run Fedora 14 on, or you can set up a VM, or you're feeling particularly adventurous and you have a fallback system in case F14 breaks your main system, please do go ahead and put F14 on there. Installing F14 direct is currently a bit tricky, but what you can do is install F13 live and then update to F14; you may have to remove a couple of packages to make this work right now, soon it should work without problems. Then you can follow the proven tester procedure exactly as you would with a released version - all the same repositories exist, fedora-easy-karma will (should!) work, and the updates go through Bodhi. Thanks a lot! Right now we have one critpath update we want to get approved ASAP - https://admin.fedoraproject.org/updates/pygtk2-2.17.0-7.fc14 . I've already filed a +1 on it, but it needs confirmation. There may be others of which I'm not yet aware. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net

1 0

Testing Fedora? Please enable SELinux if you can
by Adam Williamson 28 Jul '10

28 Jul '10

I've been asked by FESCo to post this public service announcement :) We'd just like to remind those who test Fedora, in whatever way...running a stable release with updates-testing, running Rawhide, being a proven tester (especially)...that it's best if you test with SELinux enabled and enforcing. This is the default configuration of Fedora, so we need testers to be running with this configuration so we don't miss problems that show up when SELinux is running. For proven testers, I actually added a section about this to the instructions recently - https://fedoraproject.org/wiki/Proven_tester#Testing_process . We recognize there may be situations when SELinux causes problems and you need to make it permissive or turn it off temporarily, but please try and keep it turned on if you possibly can, and if you're in a situation where you need to disable it, please let the developers know by filing a bug, so they can fix it and you can turn it back on. Thanks a lot! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net

1 0

Fedora 14 Alpha Test Compose Validation Test ( 07/29 - 08/04 )
by He Rui 28 Jul '10

28 Jul '10

Greetings Testers, I'm happy to announce that validation test event against F-14 Alpha Test Compose is coming! Similar with F-13, this time we planned testing of both Installation Process[1] and Desktop functionality[2] to ensure that they meet the F-14 Alpha Release Criteria[3]. Welcome everyone to come and join this event. Alpha TC images will be provided around Jul 29th[4] at: * http://serverbeach1.fedoraproject.org/pub/alt/stage/ Test results pages have been improved, please refer to them and follow the instructions and execute test cases inside: Installation: * https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Desktop: * https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test After you finish any test, please post your test results in the matrices from the above links. If you encounter a defect, feel free to discuss with it on IRC/Test List and file it in bugzilla if it's a bug. Please also be informed that another announcement will be sent out once Alpha TC1 is available, stay tuned! Thanks, Hurry [1] https://fedoraproject.org/wiki/QA:Installation_validation_testing [2] https://fedoraproject.org/wiki/QA:Desktop_validation_testing [3] https://fedoraproject.org/wiki/Fedora_14_Alpha_Release_Criteria [4] http://poelstra.fedorapeople.org/schedules/f-14/f-14-quality-tasks.html -- Contacts Hurry FAS Name: Rhe Timezone: UTC+8 TEL: 86-010-62608141 IRC nick: rhe #fedora-qa #fedora-zh

1 0

Fedora 14 Alpha Blocker Bug Review Meeting #1 2010-07-23 @ 16:00 UTC (12 PM EST)
by John Poelstra 22 Jul '10

22 Jul '10

When: Friday, 2010-07-23 @ 16:00 UTC (12 PM EST) Where: #fedora-bugzappers on irc.freenode.net It's that time again: blocker bug review meeting time! Friday is the SECOND blocker bug review meeting for the Fedora 14 Alpha. Here are the current bugs listed as blocking the Alpha release. We'll be discussing all of these to determine if they meet the criteria, should stay on the list, and are getting the attention they need: 615443 :: NEW :: livecd-tools :: David Huff :: boot from liveusb fails (can't mount root filesystem) :: https://bugzilla.redhat.com/show_bug.cgi?id=615443 613695 :: MODIFIED :: anaconda :: Martin Gracik :: ImportError: cannot import name GObject :: https://bugzilla.redhat.com/show_bug.cgi?id=613695 616090 :: MODIFIED :: anaconda :: Anaconda Maintenance Team :: Rescue mode fails :: https://bugzilla.redhat.com/show_bug.cgi?id=616090 If you are the owner of these bugs, kindly update the comments with your feedback as to whether you believe it is a blocker and what your plans for fixing the bug are. Do you have an issue you believe should be fixed before the Fedora 14 Alpha ships? Please consider the following criteria when escalating an issue: https://fedoraproject.org/wiki/Fedora_14_Alpha_Release_Criteria Our goal for Fedora 14, is to continue to make sure the release criteria matches up with our 'gut feelings' for what needs to be fixed before releasing. So, if you see an issue that you think should be a blocker but doesn't meet the criteria, please add it as a blocker and mention at the meeting that the criteria does't cover it. Thanks! To promote a bug for consideration as a blocker, simply add 'F14Alpha' to the "Blocks" field of the bug you are concerned about. A similar technique works for marking bugs as blocking the Beta or Final release, if appropriate, by using 'F14Beta' and 'F14Blocker' respectively. Hope to see everyone on Friday. John The command used to generate the list of bugs above is: $ bugzilla query --blocked=611990 \ --bug_status=NEW,ASSIGNED,NEEDINFO,ON_DEV,MODIFIED,POST,ON_QA,FAILS_QA,PASSES_QA,REOPENED,VERIFIED,RELEASE_PENDING \ --outputformat="%{bug_id} :: %{bug_status} :: %{component} :: %{assigned_to} :: %{summary} :: %{url}"

1 0

Please help test 389 Directory Server 1.2.6 Release Candidate 3
by Rich Megginson 06 Jul '10

06 Jul '10

The 389 team is pleased to announce the availability of Release Candidate 3 of version 1.2.6. This release contains a couple of bug fixes. ***We need your help! Please help us test this software.*** It is a Release Candidate release, so it may have a few glitches, but it has been tested for regressions and for new feature bugs. The Fedora system strongly encourages packages to be in Testing until verified and pushed to Stable. If we don't get any feedback while the packages are in Testing, the packages will remain in limbo, or get 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) The packages that need testing are: * 389-ds-base-1.2.6.rc3 - 389-ds-base More information: * Release Notes - http://port389.org/wiki/Release_Notes * Install_Guide - http://port389.org/wiki/Install_Guide * Download - http://port389.org/wiki/Download === Bugs Fixed === This release contains a few 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. * Tracking bug for 1.2.6 release - https://bugzilla.redhat.com/showdependencytree.cgi?id=543590&hide_resolved=0 ** Bug 606920 - anonymous resource limit - nstimelimit - also applied to "cn=directory manager" ** Bug 604453 - SASL Stress and Server crash: Program quits with the assertion failure in PR_Poll ** Bug 605827 - In-place upgrade: upgrade dn format should not run in setup-ds-admin.pl ** Bug 578296 - Attribute type entrydn needs to be added when subtree rename switch is on ** Bug 609256 - Selinux: pwdhash fails if called via Admin Server CGI ** Bug 603942 - null deref in _ger_parse_control() for subjectdn

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

test-announce July 2010