Search results

...1 released over the weekend, initial testing indicates it fails to boot or install successfully * pschindl updated installation results matrix template

...oods''' - begin stubbing out interoperability (dual-boot) test cases in F9 Install Test Plan ..."><td class="servermsg" colspan="2">--- | wwoods has changed the topic to: Fedora QA meeting | Followup from previous meetings</td><td><a href="#t10:02:52" c

= Fedora Release Engineering Meeting :: Monday 2007-08-13 = 1. take results from legal shove it into a voting application

* [jlaska] - copy F11 beta test results wiki changes into the wiki template (several test case additions) ** Template updated ([[QA:Fedora_11_Install_Results_Template)]] with help from wwoods a

= Fedora Release Engineering Meeting :: Monday 2007-07-23 = ..."><td class="other" colspan="2">{{Template:Tip}} f13 changed the topic of #fedora-meeting to: RELENG-Meeting - roll call</td><td><a href="#t13:01" class="tim

* [http://meetbot.fedoraproject.org/fedora-meeting/2011-04-11/fedora-qa.2011-04-11-15.00.html MeetBot summary] #* Matrix and template updated

* [http://meetbot.fedoraproject.org/fedora-meeting/2011-01-10/fedora-qa.2011-01-10-16.00.html MeetBot summary] : See {{ticket|fedora-qa|154}}

* wwoods (38) * [https://www.redhat.com/archives/fedora-test-list/2009-October/msg00194.html Proposed meeting agenda]

| name = Fedora Test Days ...#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

* Fedora 20 Beta status ...posal was viewed favourably by FESCo and [http://meetbot.fedoraproject.org/fedora-meeting/2013-10-09/fesco.2013-10-09-18.01.log.html it appears] there will b

= Fedora Release Engineering Meeting :: Monday 04-JUN-07 = * To do some final Fedora 7 tree maintenance, replace unsigned packages with signed versions

* [http://meetbot.fedoraproject.org/fedora-meeting/2011-05-16/fedora-qa.2011-05-16-15.00.html MeetBot summary] * vhumpa created a pretty text template for our future test reports (see http://vhumpa.fedorapeople.org/prettylog_u

* [http://meetbot.fedoraproject.org/fedora-meeting/2010-07-12/fedora-qa.2010-07-12-15.00.html MeetBot summary] ...e [http://poelstra.fedorapeople.org/schedules/f-14/f-14-quality-tasks.html fedora-qa schedule], a rawhide acceptance test run was scheduled for 2010-07-09.

* [https://www.redhat.com/archives/fedora-test-list/2009-October/msg00382.html Proposed meeting agenda] * [http://meetbot.fedoraproject.org/fedora-meeting/2009-10-19/fedora-meeting.2009-10-19-15.58.html meetbot summary]

...add a link from the bugzilla fields description page to the wiki page, for fedora # [jlaska] - Send informal test day feedback survey to fedora-test-list and test day participants

...Copy the source to a ''new page'' before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}} ...eport an issue with this template, file an issue in the [https://pagure.io/fedora-pgm/pgm_docs pgm_docs repo].}}

...add a link from the bugzilla fields description page to the wiki page, for fedora # [jlaska] - Send informal test day feedback survey to fedora-test-list and test day participants

* [http://meetbot.fedoraproject.org/fedora-meeting/2010-12-06/fedora-qa.2010-12-06-16.00.html MeetBot summary] : Call for ideas/owners for Fedora 15 [[QA/Test_Days]]

* Fedora 19 Alpha status == Fedora 19 Alpha status ==

#* Ball now in the fedora-release-notes court, but since Adamw is a docs team member now, he might he ...spective (aka post-mortem) yesterday (see [https://www.redhat.com/archives/fedora-test-list/2009-June/msg00503.html meeting recap]). The meeting was a cool

* [https://www.redhat.com/archives/fedora-test-list/2009-October/msg00600.html Proposed meeting agenda] * [http://meetbot.fedoraproject.org/fedora-meeting/2009-10-26/fedora-meeting.2009-10-26-16.08.html meetbot summary]

* [jlaska] email fedora-test-list@ with call for testing of rawhide installs ** Email [https://www.redhat.com/archives/fedora-test-list/2009-March/msg01022.html sent] ... a good selection of installer

= Fedora Release Engineering Meeting :: Monday 2007-11-12 = == Fedora CD Releases ==

* Fedora 20 Final status == Fedora 20 Final status ==

# Finish testing [[Releases/38/ChangeSet| Fedora 38 Changes]] ...FedoraVersion|short|38}}FinalBlocker&hide_resolved=1 {{FedoraVersion|short|38}} Final blocker bugs] as possible

* fedora alpha defect review (need url?) * '''jlaska''' - drop loop back install source cases

* [http://meetbot.fedoraproject.org/fedora-meeting/2010-04-19/fedora-qa.2010-04-19-15.00.html MeetBot summary] == Fedora 13 RC test status ==

= Fedora Release Engineering Meeting :: Monday 14-MAY-07 = * https://www.redhat.com/archives/fedora-extras-commits/2007-May/msg02800.html

[https://www.redhat.com/archives/fedora-test-list/2009-July/msg00438.html Proposed meeting agenda] # [jlaska] - Notify team list (fedora-test-list) to solicit volunteers for help with Debugging pages (see http://

= GNU Toolchain Update (glibc 2.36, binutils 2.38) <!-- The name of your change proposal --> = ...h release. Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than

*: Completed ... see announcement https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01034.html ...er the ''Keep It Simple Silly'' model, adamw recommended an email blast to fedora-test-list@ while bcc'ing maintainers involved with F11 test day. Jlaska to

| name = Fedora Test Days ...#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

* [http://meetbot.fedoraproject.org/fedora-meeting/2011-02-07/fedora-qa.2011-02-07-16.00.html MeetBot summary] : See task#19 on Fedora 15 QA calendar (http://poelstra.fedorapeople.org/schedules/f-15/f-15-qualit

= Fedora Weekly News Issue 145 = Welcome to Fedora Weekly News Issue 145 for the week ending September 28, 2008.

...dhat.com/show_bug.cgi?id=368491 368491]||Screen flicker on ATI X300 during install ...erver</code>||[https://bugzilla.redhat.com/show_bug.cgi?id=429455 429455]||Fedora 8 crashes on login (but not for all users)