Yes, it’s here again, the April Fools’ Day [1]! If you don’t have your
own plans already, let me propose one for you – participate on the
ABRT test day!
ABRT is a tool that helps reporting program crashes with a few simple
mouse clicks. It is a significant part of Fedora operating system and
its functionality is important for almost every Fedora user.
Are you curious what have ABRT developers prepared for you on the
Fool’s Day? Do you want to know what surprises are awaiting you? Then
you should come and see for your own eyes!
Help us make ABRT perfect on May 1st from 11:00 to 21:00 UTC! Visit:
https://fedoraproject.org/wiki/Test_Day:2010-04-01_ABRT
PS: This is *not* a joke :)
[1] http://en.wikipedia.org/wiki/April_Fools%27_Day
# F-13-Beta Go/No-Go meeting
# Date: 2010-04-01
# Time: 00:00 UTC (20:00 EDT, 17:00 PDT)
# Location: #fedora-meeting on irc.freenode.net
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. Release Criteria are set for each public release and are found
at https://fedoraproject.org/wiki/Fedora_Release_Criteria
For more details about this important meeting see
https://fedoraproject.org/wiki/Engineering_Readiness_Meetings
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
Thanks,
James
Event: Fedora Bug Triage Meeting
Date: 2010-03-30
Time: 15:00 UTC
Location: #fedora-meeting on irc.freenode.net
Additions or corrections to the agenda? Reply to this email.
= Agenda =
* follow ups
* open floor
Not much on the agenda this week, but I'll be there in case anyone has
topics to bring up.
Please do come out for the meeting - it'd be great to see more faces,
and we don't bite, we promise! It's a great opportunity to raise any
issues you've come across while bugzapping, or ask any questions you
might have.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
_______________________________________________
test-announce mailing list
test-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
Greetings,
As Fedora 13 marches towards a Beta, there are several Test Days planned
to help bring focused testing on upcoming features. The first,
scheduled for this Tuesday, March 30 2010, will focus on enabling SSSD
by default [1].
For those unfamiliar with SSSD, it's primary function is to provide
access to remote identity and authentication resources (think LDAP and
kerberos) through a common framework. A primary benefit is support for
offline caching of user credentials. So, why should you care?
* For starters, with offline caching, you no longer need a local
user account if you have a remote authentication service (often
the case when using remote identity/auth on laptops).
* Additionally, if you use remote authentication, it will be
managed by SSSD now [2]. So you'll want to take the live image
for a spin in your environment.
* Lastly, the new and improved system-config-authentication (aka
authconfig) is used for configuring local and remote
identity/authentication. So regardless of your setup, now is a
good time to make sure it works for you.
While testing in your own environment is desired, LDAP and Kerberos
servers are available to aid Test Day participants. As always, test
cases with clear step-by-step testing instructions will be available on
the Test Day page [1]. Also, live images will be provided to allow for
non-destructive testing on your system. The Test Day runs all
*Tuesday* in #fedora-test-day on Freenode IRC. Hope to see you there!
Thanks,
James
[1] https://fedoraproject.org/wiki/Test_Day:2010-03-30_SSSDByDefault
[2] https://fedoraproject.org/wiki/Features/SSSDByDefault
When: Friday, 2010-03-26 @ 16:00 UTC (12 PM EDT)
Where: #fedora-bugzappers on irc.freenode.net
It's that time again: blocker bug review meeting time! Tomorrow is the
first blocker bug review meeting for Fedora 13 Beta.
Here are the current bugs listed as blocking the Beta release. We'll be
discussing all of these:
574743 NEW anaconda NameError: global name 'request' is not defined
575882 NEW xorg-x11-drv-ati shortly after logging in Displays shutoff
569377 ASSIGNED anaconda CDROM install unable to eject disc - storage: error ejecting cdrom sr0: (5, 'Input/output error')
567346 ASSIGNED gnome-packagekit gpk-update-viewer does not install updates if there is any dependency issue, and does not correctly report this
574587 MODIFIED anaconda Failure to install on Intel Matrix RAID box when raid level 5 is active
576085 MODIFIED anaconda TypeError: format requires a mapping
576628 MODIFIED anaconda AttributeError: 'DMRaidMember' object has no attribute 'partedDisk'
576691 MODIFIED anaconda ValueError: Error parsing "proxy = 'intel-s3ea2-02.rhts.eng.bos.redhat.com:8080'": URL must be http, ftp or https not "intel-s3ea2-02.rhts.eng.bos.redhat.com"
575855 MODIFIED anaconda Referencing disks by-path in clearpart doesn't work
567576 ON_QA pyparted PartitionException: Could not get flag on inactive partition /dev/sda-1
572215 ON_QA qemu unhandled vm exit: 0x11 - while creating a guest using virt-install
Have an issue you'd like to propose as an F13 release blocker? Please
consider the following criteria when escalating an issue:
https://fedoraproject.org/wiki/Fedora_13_Beta_Release_Criteria
The aim for the Release Criteria for F13 is for our criteria to match up
with our 'gut feelings', 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 don't cover it. Thanks!
To promote a bug for consideration as a blocker, simply mark it as
blocking the bug 'F13Beta'. You can also already mark bugs as blocking
the Final release, if appropriate, by using 'F13Blocker'.
Hope to see everyone at the meeting!
For the record, the command used to generate the list of bugs is:
bugzilla query --blocked=538274 --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} %{summary}"
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
There will be a Printing Test Day[1] this Thursday, 2010-03-25. Have
access to a printer? Please come along and join in!
This is an opportunity to try out the new automatic printer driver
installation feature[2] in Fedora 13, as well as to give the printing
system a bit of an exercise.
For the automatic printer driver installation to work properly we need
your Device IDs! Many IDs are missing for current printers, and some
existing IDs are incorrect. You can help fix this by running following
the instructions in the test day page.
You don't need a Rawhide installation to provide useful feedback, just a
nightly live image[3] will do.
The Test Day will run all day in Freenode IRC #fedora-test-day.
Tim.
*/
[1] https://fedoraproject.org/wiki/Test_Day:2010-03-25_Printing
[2]
https://fedoraproject.org/wiki/Features/AutomaticPrintDriverInstallation
[3] http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/
Event: Fedora Bug Triage Meeting
Date: 2010-03-23
Time: 15:00 UTC
Location: #fedora-meeting on irc.freenode.net
Additions or corrections to the agenda? Reply to this email.
= Agenda =
* open floor
Nothing on the agenda this week, but I'll be there in case anyone has
topics to bring up.
Please do come out for the meeting - it'd be great to see more faces,
and we don't bite, we promise! It's a great opportunity to raise any
issues you've come across while bugzapping, or ask any questions you
might have.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net