test-announce March 2012

test-announce@lists.fedoraproject.org

9 participants
26 discussions

2012-03-30 @ 17:00 UTC - F17 Beta Blocker Bug Review #4
by Tim Flink 29 Mar '12

29 Mar '12

# F17 Beta Blocker Review meeting #4 # Date: 2012-03-30 # Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT) # Location: #fedora-bugzappers on irc.freenode.net Since F17 beta has officially slipped a week, we're having another beta blocker bug review meeting! The fourth (and hopefully final) F17 beta blocker bug review meeting will be this Friday at 17:00 UTC in #fedora-bugzappers. We'll be running through the beta blockers and nice-to-haves. An updated list of blocker bugs is available at: https://fedoraproject.org/wiki/Current_Release_Blockers. We'll be reviewing the bugs to determine ... 1. Whether they meet the beta release criteria [1] and should stay on the list 2. Whether they are getting the attention they need [1] http://fedoraproject.org/wiki/Fedora_17_Beta_Release_Criteria For guidance on Blocker and Nice-to-have (NTH) bugs, please refer to - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_nth_bug_process For the blocker review meeting protocol, see - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Tim

1 0

F17 Beta to slip by one week.
by Robyn Bergeron 29 Mar '12

29 Mar '12

At the Go/No-Go meeting it was decided to slip the Beta by one week[1]. Minutes follow below. Despite valiant efforts by many awesome people, two new blockers appeared between RC1 and RC2, for which fixes are still incoming and will require the creation of an RC3 [2]. As a result, ALL MAJOR MILESTONES, and their dependent tasks, will be pushed out by one week. Beta will now be looking at an expected release of 2012-04-10, and F17 GA is now scheduled for 2012-05-15. The adjustments to the full F17 schedule will be done (very late) tonight, and published to the Schedule wiki page[3]. Please note that the high-level milestones shown on the wiki page have already been updated to reflect the Beta slip. Thanks for your patience. We will be meeting again next Wednesday for another Go/No-Go meeting. -Robyn [1] Minutes: http://meetbot.fedoraproject.org/fedora-meeting-1/2012-03-28/f17_beta_go_no… Log: http://meetbot.fedoraproject.org/fedora-meeting-1/2012-03-28/f17_beta_go_no… [2] http://fedoraproject.org/wiki/Current_Release_Blockers [3] http://fedoraproject.org/wiki/Schedule

1 0

Announcing 389 Directory Server version 1.2.10.4 Stable
by Rich Megginson 29 Mar '12

29 Mar '12

The 389 Project team is pleased to announce the release of 389-ds-base-1.2.10.4. This release contains a fix for a bug that causes the directory server to hang when using compare operations with virtual attributes. No new features were added after alpha 8, just many bug fixes. There are also 389-adminutil, 389-admin, and 389-dsgw packages. NEW: EL6 support Beginning with RHEL 6.2, the 389-ds-base package is included in the base OS. Therefore, the 389-ds-base package can no longer be provided via EPEL, due to RHEL/EPEL packaging restrictions. However, the 389 Project will still make the full 389-ds-base package available via http://repos.fedorapeople.org/repos/rmeggins/389-ds-base. See http://directory.fedoraproject.org/wiki/Download for more information. NEW: Issue Tracking System We have moved our ticket tracking system from the Red Hat Bugzilla https://bugzilla.redhat.com/enter_bug.cgi?product=389 to our Fedora Hosted Trac https://fedorahosted.org/389. All of the old 389 bugs have been copied to Trac. All new bugs, feature requests, and tasks should be entered in Trac This link shows all of the issues fixed in the 1.2.10 branch - https://fedorahosted.org/389/report/12 In addition to the tickets for Milestone 1.2.10.3 there were a couple of issues found by valgrind that have been fixed. NEW: Plugin Authors WARNING: Plugins should be made transaction aware so that they can be called from within a backend pre/post transaction plugin. Otherwise, attempting to perform an internal operation will cause a deadlock. See http://directory.fedoraproject.org/wiki/Plugins Installation yum install --enablerepo=updates-testing 389-ds # or for EPEL yum install --enablerepo=epel-testing [--enablerepo=epel-testing-389-ds-base] 389-ds setup-ds-admin.pl Upgrade yum upgrade --enablerepo=updates-testing 389-ds-base idm-console-framework 389-admin 389-ds-console 389-admin-console 389-dsgw 389-adminutil # or for EPEL yum upgrade --enablerepo=epel-testing [--enablerepo=epel-testing-389-ds-base] 389-ds-base idm-console-framework 389-admin 389-ds-console 389-admin-console 389-dsgw 389-adminutil setup-ds-admin.pl -u How to Give Feedback The best way to provide feedback is via the Fedora Update system. * Go to https://admin.fedoraproject.org/updates * In the Search box in the upper right hand corner, type in the name of the package * In the list, find the version and release you are using (if you're not sure, use rpm -qi <package name> on your system) and click on the release * On the page for the update, scroll down to "Add a comment" and provide your input Or just send us an email to 389-users(a)lists.fedoraproject.org Reporting Issues https://fedorahosted.org/389 More Information * 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 17 Beta Release Candidate 2 (RC2) Available Now!
by Andre Robatino 28 Mar '12

28 Mar '12

As per the Fedora 17 schedule [1], Fedora 17 Beta Release Candidate 2 (RC2) is now available for testing. Content information, including changes, can be found at https://fedorahosted.org/rel-eng/ticket/5141 . Please see the following pages for download links (including delta ISOs) and testing instructions. Normally dl.fedoraproject.org should provide the fastest download, but download-ib01.fedoraproject.org is available as a mirror (with an approximately 1 hour lag) in case of trouble. To use it, just replace "dl" with "download-ib01" in the download URL. Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Base: https://fedoraproject.org/wiki/Test_Results:Current_Base_Test Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Ideally, all Alpha and Beta priority test cases for Installation [2], Base [3], and Desktop [4] should pass in order to meet the Beta Release Criteria [5]. Help is available on #fedora-qa on irc.freenode.net [6], or on the test list [7]. Create Fedora 17 Beta release candidate (RC) - live and traditional https://fedorahosted.org/rel-eng/ticket/5141 F17 Beta Blocker tracker bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=752649 F17 Beta Nice-To-Have tracker bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=752652 [1] http://rbergero.fedorapeople.org/schedules/f-17/f-17-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Installation_validation_testing [3] https://fedoraproject.org/wiki/QA:Base_validation_testing [4] https://fedoraproject.org/wiki/QA:Desktop_validation_testing [5] https://fedoraproject.org/wiki/Fedora_17_Beta_Release_Criteria [6] irc://irc.freenode.net/fedora-qa [7] https://admin.fedoraproject.org/mailman/listinfo/test

2 1

Test Day 2012-03-29: GNOME Shell Software Rendering
by Kamil Paral 27 Mar '12

27 Mar '12

There will be a "GNOME Shell Software Rendering" Test Day on Thursday! https://fedoraproject.org/wiki/Test_Day:2012-03-29_Gnome_Shell_Software_Ren… Here's an introduction from Vitezslav Humpa, who's in charge of this event from QA perspective: This week brings a second installment of Fedora Test Day targeting GNOME 3. This time we will focus on software rendering providing a full GNOME session purely by means of the CPU. Nowadays with most of personal computers capable of hardware 3D acceleration this might seem unnecessary. But let's not forget a whole lot of us who have capable but yet unsupported hardware and get stuck with the Fallback mode. And this is not the only case. In addition to computers with obsolete graphics there are VM hypervisors like KVM or VirtualBox that don't support full 3D yet. Fedora can also run on many kinds of less usual devices like tablets or netbooks that don't have free (or even proprietary) drivers ready. Simply said, our goal is to make sure that no matter what hardware you are running your Fedora on, you will always get the user experience you are entitled to - a full GNOME desktop. Do you have an older PC? Netbook? Or do you like to play with the latest of the latest in VM, where it won't "break" your computer? Even if not, please help us test the GNOME Shell software rendering by following few test cases and catching a few bugs - after all, as always with Fedora, you'll be doing that for yourself :-) Date: 2012-03-29 Time: all day What: https://fedoraproject.org/wiki/Test_Day:2012-03-29_Gnome_Shell_Software_Ren… Where: #fedora-test-day

1 0

Kdump Test Day on Mar 27
by Hongqing Yang 26 Mar '12

26 Mar '12

Greetings, Today is the another test day for Fedora 17 Beefy Miracle. All the events take place in #fedora-test-day on Freenode IRC. As always, the more testing we can get, the better. Kernel developers and QA team members will be on hand to help with testing and debugging. The testing is easy and there are full instructions on the wiki pages. You don't need a Fedora account to do the testing or to file the results, but you will need a Bugzilla account to file bugs. To join in, just follow the test instructions, then add your results to the table at the bottom of the page - there are instructions on how to do it. You can join #fedora-test-day to chat with the QA team and the developers. Please come along and help us make sure Fedora 17's success! [1] https://fedoraproject.org/wiki/Test_Day:2012-03-27_Kdump Hongqing

1 0

Fedora 17 Beta Go/No-Go Meeting, Wednesday, March 28, @17:00 Eastern
by Robyn Bergeron 26 Mar '12

26 Mar '12

Please join us on irc.freenode.net in #fedora-meeting-1 for this important meeting. Will the Beefy Miracle live up to the latter half of its name? Attend this meeting and find out! :) Wednesday, March 28, 2012 @21:00 UTC (17:00 EDT/14:00 PDT) "Before each public release Development, QA and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the Go/No-Go Meeting." "Verifying that the Release criteria are met is the responsibility of the QA Team." For more details about this meeting see: https://fedoraproject.org/wiki/Go_No_Go_Meeting In the meantime, keep an eye on the Fedora 17 Beta Blocker list: http://fedoraproject.org/wiki/Current_Release_Blockers Ongoing Beta RC test results can be seen here: https://fedoraproject.org/wiki/Category:Fedora_17_Beta_RC_Test_Results Cheers! (And do note that we will be in #fedora-meeting-1!) -Robyn

1 0

2012-03-26 @ 15:00 UTC - Fedora QA Meeting
by Adam Williamson 26 Mar '12

26 Mar '12

# Fedora Quality Assurance Meeting # Date: 2012-03-26 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! It's meeting time once more. We have a beta to sign off on, so expect lots of happy fun blocker review. Also, I figured it'd be a good idea to kick around the 'QA as a sub-project' topic in a meeting. This is a reminder of the upcoming QA meeting. Please add any topic suggestions to the meeting wiki page: https://fedoraproject.org/wiki/QA/Meetings/20120326 The current proposed agenda is included below. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 17 Beta status / blocker review 3. 'Project' status 4. Test Day report 5. Upcoming QA events 6. AutoQA update 7. Open floor -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

1 0

Fedora 17 Beta Release Candidate 1 (RC1) Available Now!
by Andre Robatino 23 Mar '12

23 Mar '12

As per the Fedora 17 schedule [1], Fedora 17 Beta Release Candidate 1 (RC1) is now available for testing. Content information, including changes, can be found at https://fedorahosted.org/rel-eng/ticket/5141 . Please see the following pages for download links (including delta ISOs) and testing instructions. Normally dl.fedoraproject.org should provide the fastest download, but download-ib01.fedoraproject.org is available as a mirror (with an approximately 1 hour lag) in case of trouble. To use it, just replace "dl" with "download-ib01" in the download URL. Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Base: https://fedoraproject.org/wiki/Test_Results:Current_Base_Test Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Ideally, all Alpha and Beta priority test cases for Installation [2], Base [3], and Desktop [4] should pass in order to meet the Beta Release Criteria [5]. Help is available on #fedora-qa on irc.freenode.net [6], or on the test list [7]. Create Fedora 17 Beta release candidate (RC) - live and traditional https://fedorahosted.org/rel-eng/ticket/5141 F17 Beta Blocker tracker bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=752649 F17 Beta Nice-To-Have tracker bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=752652 [1] http://rbergero.fedorapeople.org/schedules/f-17/f-17-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Installation_validation_testing [3] https://fedoraproject.org/wiki/QA:Base_validation_testing [4] https://fedoraproject.org/wiki/QA:Desktop_validation_testing [5] https://fedoraproject.org/wiki/Fedora_17_Beta_Release_Criteria [6] irc://irc.freenode.net/fedora-qa [7] https://admin.fedoraproject.org/mailman/listinfo/test

1 0

Fedora 17 QA Retrospective page is up
by Adam Williamson 23 Mar '12

23 Mar '12

Hey, everyone. I'm sorry this is late, my bad for not getting it up earlier. :( The Retrospective page for Fedora 17 QA is now up: https://fedoraproject.org/wiki/Fedora_17_QA_Retrospective We use the retrospective page to track things that went well and things that didn't go so well during the Fedora 17 validation process, and for tracking ideas we have but don't have time to act on during the rush of doing validation (that's the wishlist). Please, add any feedback you have of this type to the retrospective page! There are instructions on the page for adding feedback. All feedback is useful, and once 17 validation is done, we'll take a look at all the items on the page and come up with specific recommendations for addressing them which we'll file as trac tickets and work on in the time before Fedora 18 validation starts up. We've been doing this for a while now and it's turned out to be a great way to keep constantly improving our processes. You can look at the previous pages for inspiration: https://fedoraproject.org/wiki/Category:QA_Retrospective And I'll copy/paste James' old list of leading questions to prompt feedback (thanks, James!): 1. Were you able to participate in any Fedora 17 Alpha, Beta or Final test runs? 2. What worked well, what prevented you from participating, were instructions clear? 3. What worked (or didn't work) well about Fedora Test Days this release? 4. Are you a maintainer, why do you think your critpath updates haven't been tested? What could you do to encourage more testing of your proposed updates? 5. Did you escalate any bugs for consideration as {Alpha,Beta,Final} release Blockers? Why not? Was the process well documented and did it make sense? 6. Did you attend or contribute to any Fedora blocker meetings? Why not? What did you like, dislike? What prevented you from participating? 7. Did you find any of the release criteria changes or validation test extensions particularly useful or problematic? 8. Can you think of any obviously important areas we are not currently covering in the validation tests and criteria? 9. Unlimited time and resource ... what do you think the the QA team should focus on for Fedora 18 and beyond </pony> -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

test-announce March 2012