test-announce November 2011

test-announce@lists.fedoraproject.org

4 participants
16 discussions

Very belated 2011-09 Graphics Test Week recap
by Adam Williamson 30 Nov '11

30 Nov '11

I know this is horribly late, but I just worked my way around to it! Sorry for that. Here's the recap of the Fedora 16 Graphics Test Week. The overall numbers of tests done and bugs filed are down significantly, because I was very busy and did not do a great job of arranging and promoting the events this cycle. I hope we'll be able to do a better job for the Fedora 17 graphics test week. Here's the numbers on tests conducted and bugs filed. I counted each non-example line in the main results matrix as a 'test conducted'. I didn't count the runs in the 'bonus' 3D matrix, in order to provide a more fair comparison with previous releases. This might affect the bugs-to-tests ratio somewhat. f11 nouveau: 104 tests, 42 bugs - ratio 0.40 f12 nouveau: 53 tests, 34 bugs - ratio 0.64 f13 nouveau: 78 tests, 26 bugs - ratio 0.33 f14 nouveau: 39 tests, 8 bugs - ratio 0.21 f15 nouveau: 83 tests, 55 bugs - ratio 0.66 f16 nouveau: 16 tests, 8 bugs - ratio 0.50 f11 radeon: 55 tests, 46 bugs - ratio 0.84 f12 radeon: 61 tests, 81 bugs - ratio 1.33 f13 radeon: 48 tests, 33 bugs - ratio 0.69 f14 radeon: 32 tests, 18 bugs - ratio 0.56 f15 radeon: 66 tests, 38 bugs - ratio 0.58 f16 radeon: 12 tests, 8 bugs - ratio 0.67 f11 intel: 23 tests, 21 bugs - ratio 0.91 f12 intel: 29 tests, 31 bugs - ratio 1.07 f13 intel: 38 tests, 38 bugs - ratio 1.00 f14 intel: 33 tests, 28 bugs - ratio 0.84 f15 intel: 37 tests, 25 bugs - ratio 0.68 f16 intel: 10 tests, 7 bugs - ratio 0.70 It's hard to draw any conclusions from such small numbers, but really, none of them are far out of line with previous events. Here's the chart for how reported bugs are handled, adding the results from the F15 events (this chart gets updated on a one-cycle delay, because it's concerned with how the bugs filed are handled after a reasonable amount of time for the developers to look at them). A full explanation of what this tracks and how it's calculated in the F13 recap at https://lists.fedoraproject.org/pipermail/test/2010-April/090271.html . Some resolutions showed up this time that didn't before. I counted 'WORKSFORME' in with 'closeddupe' - i.e. as part of the set of bugs that should just be completed discarded from consideration. I handled 'UPSTREAM' bugs on a case-by-case basis, going in and look at whether they'd actually been fixed upstream or what, and putting them in the most appropriate group. Also, if you try to reproduce these numbers, note that you'll want to remove the bugs 123456 and 234567 from the lists - they're used in the 'example' entries in the results matrix. The bug totals are slightly different from the above chart because I copy/pasted the F15 numbers in the above chart from the last recap, but the numbers in this chart are newly generated, and so a few bugs that were filed and added to the Wiki pages *after* the last recap went out have been added to the numbers in this chart. f11 nouveau: 42 bugs, 4 open, 8 closeddupe, 24 closedfixed, 6 closedunfixed - 70.59% f12 nouveau: 34 bugs, 11 open, 8 closeddupe, 14 closedfixed, 1 closedunfixed - 53.85% f13 nouveau: 27 bugs, 17 open, 6 closeddupe, 3 closedfixed, 1 closedunfixed - 14.29% f14 nouveau: 8 bugs, 5 open, 3 closeddupe - 0% (small sample) f15 nouveau: 58 bugs, 27 open, 13 closeddupe, 13 closedfixed, 5 closedunfixed - 28.89% f11 radeon: 46 bugs, 14 open, 10 closeddupe, 19 closedfixed, 3 closedunfixed - 52.78% f12 radeon: 81 bugs, 19 open, 32 closeddupe, 28 closedfixed, 2 closedunfixed - 57.14% f13 radeon: 36 bugs, 28 open, 3 closeddupe, 5 closedfixed, 0 closedunfixed - 15.15% f14 radeon: 18 bugs, 13 open, 0 closeddupe, 3 closedfixed, 2 closedunfixed - 16.67% f15 radeon: 38 bugs, 17 open, 10 closeddupe, 9 closedfixed, 2 closedunfixed - 32.14% f11 intel: 21 bugs, 7 open, 1 closeddupe, 12 closedfixed, 1 closedunfixed - 60% f12 intel: 31 bugs, 7 open, 12 closeddupe, 12 closedfixed, 0 closedunfixed - 63.16% f13 intel: 42 bugs, 26 open, 4 closeddupe, 11 closedfixed, 1 closedunfixed - 28.95% f14 intel: 28 bugs, 21 open, 4 closeddupe, 1 closedfixed, 2 closedunfixed - 4.17% f15 intel: 27 bugs, 8 open, 7 closeddupe, 12 closedfixed, 0 closedunfixed - 60% There's definitely good news here - as noted in the last recap, we had a good crop of reports from the F15 event, so there's no reason we shouldn't be able to get back up to this level with better organization and promotion for F17. Also, the number of bugs actually getting *fixed* - which is the ultimate goal of the event - was significantly higher than F13 and F14, not quite back to F11/F12 levels, but a lot better. So the trend of fewer bugs getting fixed seems to have been stopped during F15 cycle. Intel showed a particularly marked improvement here. (It's worth noting that some of the bugs filed and fixed were actually on GNOME rather than the X drivers; I didn't compare the level of non-X bugs in the results in other releases, so that is an untracked variable. If anyone wants to look into that, please do!) Many thanks as always to all those who contributed tests and to our plucky X developers and triagers, especially: Adam Jackson Dave Airlie Jerome Glisse Ben Skeggs Matej Cepl The raw list of bugs filed at each of the F16 events follows. Nouveau ------- 735703 NEW - VT now working properly with the nouveau driver 692035 NEW - [NV94] Dual-head problems: Nouveau on FC14 fails to drive both outputs of Nvidia 9600GT correctly. 735702 NEW - [NV67] fast switch user was not working 735893 NEW - [NV42] Shadows on rendering 736323 NEW - startx starts fallback mode 736837 CLOSED WORKSFORME - Rotate display fails on GTX 560 737850 CLOSED DUPLICATE - nouveau testday: focus issues while glx testcase (NV43) 735770 CLOSED NOTABUG - [NVa8] External monitor doesn't work after upgrade to F16 Radeon ------ 735703 NEW - VT now working properly with the nouveau driver 698711 NEW - [Crestline] Generic video multihead test failure 735702 NEW - [NV67] fast switch user was not working 733857 NEW - No display with AMD A6-3650 APU (ATI HD 6530D) 736498 NEW - [RV635] Testcase radeon xv failed 736562 NEW - [RS740] Gnome 3 dualhead fallback mode 739078 CLOSED ERRATA - Booting to runlevel 3 failed 698011 CLOSED UPSTREAM - [RS690] LiveCD doesn't boot into Gnome3. Only get background, no panel. Mouse clicks ignored. Intel ----- 736859 NEW - dual-head: re-arranging screen leaves one screen off 736358 NEW - Gtk-WARNING **: Unknown property: GtkDialog.has-separator 735702 NEW - [NV67] fast switch user was not working 734265 NEW - [abrt] gnome-shell-3.1.4-2.gite7b9933.fc16: __GI_raise: Process /usr/bin/gnome-shell was killed by signal 6 (SIGABRT) 736323 NEW - startx starts fallback mode 736330 NEW - [Cantiga] Internal display turned off when playing game in dual monitor setup 736846 CLOSED CURRENTRELEASE - user switching with color manager enabled causes segfaults and gnome "Oh no..." -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

1 0

AutoQA Upgrade to 0.7
by Tim Flink 30 Nov '11

30 Nov '11

As a heads up, we're updating AutoQA to 0.7 today. I'm not expecting any issues during the update process but no new jobs will be run while we're updating the production systems. The update process shouldn't take much more than an hour, maybe two if we hit problems. If all goes well, you might notice a delay in results being posted to bodhi. If all doesn't go well, you'll see another email from me. Tim

1 0

Fedora 16 QA Retrospective: recommendations filed, tickets up for grabs!
by Adam Williamson 29 Nov '11

29 Nov '11

Hi, folks. I wanted to let everyone know that I've gone through all the issues raised in the Fedora 16 QA Retrospective: https://fedoraproject.org/wiki/Fedora_16_QA_Retrospective and taken action on each item where possible. For most items I've added a recommendation to the Recommendations section: https://fedoraproject.org/wiki/Fedora_16_QA_Retrospective#Recommendations so that section now lists the trac tickets (in most cases) and mailing list threads relevant to each item. I've also brought forward some still-outstanding action items from the F15 retrospective, listed under 'Brought forward from Fedora_15_QA_Retrospective' sub-sections within the Recommendations. Here's a list of the specific tasks that are now outstanding in QA trac as a direct result of the Retrospective: it would be great if people could volunteer to pick these up. Please, if you'd like to help out, just assign one of the tickets to yourself and go do it! There are no hoops to jump through. I'll try and add links in each ticket to the relevant processes for creating test cases and so on. * http://fedorahosted.org/fedora-qa/ticket/256 "Add EFI data to installation / base results matrices" * http://fedorahosted.org/fedora-qa/ticket/257 "Create and maintain F17 install test plan" * http://fedorahosted.org/fedora-qa/ticket/258 "Create EC2 test cases and integrate into validation matrices" * http://fedorahosted.org/fedora-qa/ticket/259 "Review Fedora 17 feature list and co-ordinate with owners of significant features to create test plans" * http://fedorahosted.org/fedora-qa/ticket/260 "Cover USB-written images better in installation validation testing" * http://fedorahosted.org/fedora-qa/ticket/261 "Revise upgrade test case set" There were a couple of items where the action didn't really fit comfortably into the 'Recommendations' section, so for the record, I'll list those here: "adamw - when there are showstoppers in anaconda early we tend to just sit around and wait for them to get fixed, but without much urgency; which means we're getting no idea of what bugs are lurking behind the showstoppers, and we wind up trying to fix a lot of blockers in a small amount of time once the showstoppers are finally fixed" "adamw - when we hit an obvious showstopper we tend to focus in on it exclusively until it's fixed, iterate, and then be surprised when there are bugs hidden behind it; we should work harder to try and workaround showstoppers in a way that has as small an impact as possible, and continue testing, to avoid this problem. e.g. RHBZ #730863 hid behind RHBZ #729563, but we could have exposed it by editing /etc/selinux/config in the installed system prior to rebooting from the installer" "adamw - need to do more direct personal pinging of maintainers who seem unresponsive to blockers; some respond when contacted directly but do not appear to place a high priority on bug reports" There isn't really any specific action to be taken on these right now, they're more things to keep in mind while validating F17. items 5-8 are just notes of what bugs blocked Alpha RC spins, no specific action was really needed in relation to any of those "adamw - it wasn't an A+ idea for both rpm maintainers to be on vacation at the same time, with no cover in place, during a critical freeze period" The action I took here was fairly RH-internal, as this is really an RH staffing issue: I poked Tom Callaway to ask about putting a cover policy in place for RH-employed maintainers of key Fedora components "adamw - NFS testing instructions may need to be more precise to avoid pilot errors, and may need to account for NFSv4 quirks" This one's pretty much already taken care of, we did tweak the NFS test cases somewhat during the f16 cycle "tflink - Maybe it was due to the high number of TC/RC spins that we did for F16 but it would be awesome to have some more automation around image generation for testing. I'm not talking about any rel-eng processes but it would be nice to be able to request generation of a boot.iso made from custom packages and packages in koji in order to do testing. I can see this being helpful for test day coordination as well but there are issues with complexity and hosting so this is a bit of a "pony list" item." "tflink - Since qemu/kvm VMs are all legacy BIOS emulation, it would be awesome to do EFI emulation. There are some projects out there on using EFI in qemu VMs but it is unknown whether they actually work. Either way, it might be good to look into them in order to evaluate whether their use is practical" These are sort of 'blue sky' ideas from tflink that don't lead to any immediate action items that anyone could take care of: I'm relying on him to keep thinking about them and turn them into more concrete proposals. I don't really want to file open-ended tickets for rough ideas. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

1 0

2011-11-28 @ 16:00 UTC - Fedora QA Meeting
by Adam Williamson 25 Nov '11

25 Nov '11

# Fedora Quality Assurance Meeting # Date: 2011-11-28 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! 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/20111128 The current proposed agenda is include below. If no topics beyond the standard "Previous meeting follow-up" and "AutoQA update" topics are present or proposed, the meeting will be canceled. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Revised F17 schedule confirmation 3. F16 retrospective activity 4. AutoQA update 5. Open Discussion - <your topic here> -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

1 0

FUDCon Blacksburg subsidies announcement, and general planning update.
by Robyn Bergeron 21 Nov '11

21 Nov '11

Greetings everyone, A few updates on the upcoming FUDCon in Blacksburg, VA in January 2012: * We will be having our second subsidy meeting on Wednesday, November 23rd. This meeting will be for evaluating and processing any available subsidy monies for international attendees, as well as processing any new North America-based subsidy requests. If you are requesting a subsidy, please ensure that your Trac ticket for requesting subsidies is complete, particularly and especially with detail to what you plan to accomplish / do while at FUDCon. With more than ten international requests, and limited funding, it is especially important for the people attending the meeting to have a clear picture of your plans in order to make a decision on funding. The subsidy meeting is open for anyone to attend. Please feel free to participate, especially if you have requested funding, so that we may ask questions and get answers in a timely manner. The meeting occurs this Wednesday (during the normal FUDCon planning meeting time) at 17:00 UTC in #fedora-meeting on irc.freenode.net (9am Pacific, Noon Eastern). For more information on applying for a subsidy, please read https://fedorahosted.org/fudcon-planning/wiki/FundingRequest * Pre-registration for FUDCon is open. If you are planning to attend, please visit the event wiki page at http://fedoraproject.org/wiki/FUDCon:Blacksburg_2012 to add your name to the registration list. * Rooms at the hotel for FUDCon can be booked now. The block is open until December 28, 2011. Details on booking your room can be seen here: https://fedoraproject.org/wiki/FUDCon:Blacksburg_2012#Lodging_.2F_Hotel * As always, your participation is welcomed, and your help is appreciated. Signing up on the fudcon-planning mailing list is a great way to find out how you can help, and to get more details about FUDCon as the event draws near. Sign up at https://admin.fedoraproject.org/mailman/listinfo/fudcon-planning to get on the list. Thanks, and I hope to see you at FUDCon! :) -Robyn

1 0

2011-11-21 @ 16:00 UTC - Fedora QA Meeting
by Adam Williamson 21 Nov '11

21 Nov '11

# Fedora Quality Assurance Meeting # Date: 2011-11-22 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! 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/20111121 The current proposed agenda is include below. If no topics beyond the standard "Previous meeting follow-up" and "AutoQA update" topics are present or proposed, the meeting will be canceled. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. FUDCon NA hackfest planning 3. Fedora 17 Test Day planning 4. Upcoming QA events 5. AutoQA update 6. Open Discussion - <your topic here> -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

1 0

Announcing the release of Fedora 16.
by Robyn Bergeron 08 Nov '11

08 Nov '11

The Fedora Project is pleased to announce the release of Fedora 16 ("Verne"). Fedora is a leading-edge, free and open source operating system that continues to deliver innovative features to many users, with a new release about every six months. Fedora 16 brings exciting new features for desktop users, for system administrators, and for developers. Highlights of these features can be found below. If the mere mention of Fedora 16 is all you need, download options can be found at: http://fedoraproject.org/get-fedora For detailed information, see the release notes: http://docs.fedoraproject.org/en-US/Fedora/16/html/Release_Notes/ == Dedication== During the preparation of Fedora 16, the computing world lost one of its great contributors: Dennis Ritchie. Ritchie co-invented Unix and the C language. He also co-authored The C Programming Language, a book that taught many programmers just at the time personal computing was exploding. Without Ritchie computing would be nothing like it is today. A humble man, not well-known outside his field, Dennis will always be remembered by those of us who practice the craft. Thank you, Dennis. == What's New in Fedora 16? == For desktop users: a journey to the center of the desktop... * GNOME 3.2, the latest update to the most popular desktop environment, brings new features, including: o System Settings gains an "Online Accounts" panel, which provides a central point for managing online accounts like Google, Facebook, etc. o A new contact management application is integrated with Empathy, Evolution and the new "Online Accounts" settings panel o A new document management application provides a simpler alternative to traditional file management for both local and "in-cloud" documents. * KDE 4.7, the most recent version of this feature-rich desktop environment, brings substantial updates, including: o DigiKam 2.0 adds face detection and recognition, geotagging and more. o An updated Plasma Workspaces window manager (KWin) makes KDE better suited for mobile devices, and also adds improvements for desktop users. o A new shutdown dialog allows users with multiple operating systems to select the OS to boot next. For developers: Twenty thousand lines in C... * Perl 5.14, a new version of Perl, brings many enhancements, including Unicode 6.0 support. * GCC Python Plugins extend GCC with Python 2 and 3, without dealing with the C internals of GCC. * D2: Fedora 16 is the first Linux distribution to include the newest version of D, a systems programming language combining the power and high performance of C and C++ with the programmer productivity of modern languages such as Ruby and Python. For system administrators: around the world in eighty columns... * GRUB2: This leap forward allows better configuration options and better support for non-x86 architectures. * New system account ID numbering: Fedora 16 starts user IDs at 1000, providing more room for system accounts and making it easier for administrators not have services run as root. This improves interoperability with other Linux distributions that start user IDs at 1000. * Chrony: Chrony provides network time protocol (NTP) client and server pieces which are more tolerant of unstable clocks and Internet connections which are not always on. * ext4 driver mounts ext2 and ext3: Fedora 16 uses the ext4 driver to mount ext2 and ext3 file systems, reducing the size of the kernel code. * Improved virtualization tools: o Fedora 16 provides improvements to virtual networking, making large deployments easier. o Virt-manager guest inspection is a unique-to-Fedora tool allowing read-only access to guest file systems, applications, and Windows registry. o Fedora 16 provides locking of virtual disks to prevent a disk being used by multiple virtual machines simultaneously. * Cloud goodies galore: o Aeolus, a cross-cloud Infrastructure-as-a-Service (IaaS) platform, which consists of a web-based user interface and tools for managing cloud instances across heterogenous clouds. o OpenStack, another IaaS platform, which takes form as a collection of services for setting up and running a cloud compute and storage infrastructure. o Pacemaker-cloud, which provides application service high availability for cloud environments. o HekaFS, a cloud-ready version of GlusterFS, which extends the filesystem to be suitable for deployment by a cloud provider by adding in stronger authentication and authorization, encryption, and multi-tenancy. This is only a taste of what is included in Fedora 16. A more detailed list can be found at: https://fedoraproject.org/wiki/Releases/16/FeatureList == Download and Upgrade == Fedora 16 is not science fiction. It is here right now: http://get.fedoraproject.org To launch Fedora 16 instances in the cloud, refer to: http://fedoraproject.org/wiki/Cloud_images If you are upgrading from a previous release of Fedora, refer to: http://fedoraproject.org/wiki/Upgrading Fedora 16 full release notes and guides for several languages are available at: http://docs.fedoraproject.org/ Fedora 16 common bugs are documented at: https://fedoraproject.org/wiki/Common_F16_bugs == Fedora Spins == Fedora spins are alternate version of Fedora, tailored for various types of users via hand-picked application set or customizations. They can be found at: http://spins.fedoraproject.org == Contributing == There are many ways to contribute beyond bug reporting. You can help translate software and content, test and give feedback on software updates, write and edit documentation, design and do artwork, help with all sorts of promotional activities, and package free software for use by millions of Fedora users worldwide. To get started, visit http://join.fedoraproject.org today! == Contact information == Journalists and reporters can find additional information at: https://fedoraproject.org/wiki/Press

1 0

2011-11-07 @ ** 16:00 UTC ** - Fedora QA Meeting
by Adam Williamson 07 Nov '11

07 Nov '11

UPDATE: As Kamil pointed out, I screwed up the time thing entirely in the initial announcement for this meeting. So here's a corrected version. We will adjust the meeting time for DST changes just as we did last year, starting this week. So the meeting is at 16:00 UTC, which means that if your clocks changed this weekend, the meeting is at *the same time as always* as far as your local time is concerned. If your clocks didn't go back this weekend, the meeting will be one hour later in your local time. Hope that's clear! If you're unsure, just do 'date -u' at a console and it'll tell you what time it is in UTC right at the moment you run the command, and you can figure it out from there. Sorry for any confusion. WHAT: Fedora QA Meeting WHEN: 16:00 UTC (11:00 EST, 08:00 PST) WHERE: #fedora-meeting It's meeting time again! It's the first meeting of the post-Fedora 16 era, so time to dust off anything you've been sitting on through the release crunch. If anyone has anything to add to the agenda, please reply to this mail, and I will add it. Thanks! Proposed agenda: * Previous meeting follow-up [1] * F16 release planning: common bugs, retrospective, etc * FESCo plan to drop proven tester process * Fedora 17 pre-planning: anaconda GUI rewrite * AutoQA update * Upcoming QA Events * Open discussion If you have any suggested topics, feel free to respond to this email or bring them up during open discussion. [1] http://meetbot.fedoraproject.org/fedora-meeting/2011-10-31/fedora-qa.2011-1… -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

1 0

F16 release issue: karma required for livecd-tools updates
by Adam Williamson 07 Nov '11

07 Nov '11

Hey, everyone. There are pending updates for livecd-tools in F14, F15 and F16: https://admin.fedoraproject.org/updates/FEDORA-2011-15442 https://admin.fedoraproject.org/updates/FEDORA-2011-15374 https://admin.fedoraproject.org/updates/FEDORA-2011-15386 It's quite important that we get these approved, as they prevent a potential problem with Fedora 16. The final F16 blocker was the bug where the bootloader would be installed to the USB key if you tried to update from F15 using the DVD / net install ISO written to a USB key: this bug can actually still happen if you write the USB key without the --format parameter. The update makes livecd-iso-to-disk relabel the USB stick even if --format is not used, to avoid the problem (we hope). Please test it and provide karma! If you want to check whether it truly fixes the bug, here's the procedure: 1. *Before* updating livecd-tools, write the F16 DVD or net install ISO to USB using livecd-iso-to-disk *without* the --format parameter . Don't use a USB stick you've already written a Fedora image onto before, or if you must use such a stick, reformat it first, so it doesn't have LIVE as its partition label. 2. Install Fedora 15 onto your test system 3. Use the USB stick to try and upgrade the Fedora 15 installation 4. At the 'what to do with the bootloader' screen, pick the default 'install new bootloader configuration option' 5. At the 'where to write the bootloader' screen, note which device anaconda will allow you to write to the MBR of: if it's the USB key, you've successfully reproduced the bug. If it's not the USB key, your key is probably failing the 'is this device a valid bootloader target?' test for some other reason 6. Assuming you managed to reproduce the bug, update livecd-tools, and repeat the entire test, writing the USB stick with the updated livecd-tools this time: it should prevent the bug from occurring This is the full test to see whether it actually fixes the problem. You can also check the partition label on the stick after livecd-iso-to-disk before and after the update. The non-updated livecd-iso-to-disk should leave whatever partition label was on the USB stick before, when you write an image without --format; the updated one should change the label to LIVE. Well, I know it's a slightly complex issue, but hope you followed that, and please karma up the updates! Thanks :) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

1 0

2011-11-07 @ 15:00 UTC - Fedora QA Meeting
by Adam Williamson 07 Nov '11

07 Nov '11

WHAT: Fedora QA Meeting WHEN: 15:00 UTC (12:00 EST, 09:00 PST) WHERE: #fedora-meeting It's meeting time again! It's the first meeting of the post-Fedora 16 era, so time to dust off anything you've been sitting on through the release crunch. Also note that clocks went back in North America today, but we do not change the meeting time, so it may be an hour later for you now. I don't know where else in the world the clock change happened, but if it changed for you this weekend, remember the meeting's an hour later. If anyone has anything to add to the agenda, please reply to this mail, and I will add it. Thanks! Proposed agenda: * Previous meeting follow-up [1] * F16 release planning: common bugs, retrospective, etc * FESCo plan to drop proven tester process * Fedora 17 pre-planning: anaconda GUI rewrite * AutoQA update * Upcoming QA Events * Open discussion If you have any suggested topics, feel free to respond to this email or bring them up during open discussion. [1] http://meetbot.fedoraproject.org/fedora-meeting/2011-10-31/fedora-qa.2011-1… -- 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 November 2011