Search results

=== Alpha blocker bug day#2 === ...dora-test-list/2009-July/msg00429.html). Some discussion followed about a Alpha blocker {{bz|513020}}

.... See [http://lists.fedoraproject.org/pipermail/test/2010-May/091311.html announcement] and [https://fedorahosted.org/autoqa/wiki/initscripts instructions] and [h * 2010-07-08 - Pre-Alpha Rawhide Acceptance Test Plan #1

* Contingency deadline: Probably Fedora 25 Alpha freeze <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> <!-- When your change proposal page is completed and ready for review and announcement -->

Builds for Fedora 26 Alpha can be found here: http://dl.fedoraproject.org/pub/fedora/linux/releases/te <!-- When your change proposal page is completed and ready for review and announcement -->

...the basis of Fedora 11 Alpha. Only targeted fixes will be pulled into the Alpha tag after the freeze. Rawhide itself will continue on as to not disrupt de ...effort to turn that freeze into something usable. PLEASE wait until after Alpha has been cut to do this." He seemed slightly mollified[3] by Tomas' use of

* Contingency deadline: Alpha freeze. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> <!-- When your change proposal page is completed and ready for review and announcement -->

.... See [http://lists.fedoraproject.org/pipermail/test/2010-May/091311.html announcement] and [https://fedorahosted.org/autoqa/wiki/initscripts instructions] and [h * 2010-07-08 - Pre-Alpha Rawhide Acceptance Test Plan #1

* Contingency deadline: Alpha freeze. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> <!-- When your change proposal page is completed and ready for review and announcement -->

* Contingency deadline: F26 Alpha Freeze <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> <!-- When your change proposal page is completed and ready for review and announcement -->

* Contingency deadline: Before alpha <!-- When your change proposal page is completed and ready for review and announcement -->

* Better announcement of test days, also with more than 2 days ahead of time. Maybe some RSS feed # While all announcement channels used were recognized by respondents, several suggestions indicated

...ove from the venerable ''bugzilla-2.18'' to ''bugzilla-3.2''. The original announcement[1] was posted on several lists and detailed the planned outage and the chan The announcement and the reminder[2] that this would all happen on 2nd August requested that

In Announcement, we have "Cast your vote for the Fedora 9 Codename!" "Woah, it’s the 18th of January 2008 - Fedora 9 Alpha is not even out yet but the first developer interview of the new year is! T

...nt|Fedora 13 QA Retrospective|Ideas have already been coming in since F-13-Alpha. It's not too early to note QA issues you felt where handled '''well''', o * 2010-01-21 - [[Test_Results:Fedora_13_Rawhide_Acceptance_Test_1|Pre-Alpha Rawhide Acceptance Test Plan #1]]

* Contingency deadline: Alpha <!-- When your change proposal page is completed and ready for review and announcement -->

In Announcements, we have "Announcing Fedora 9 Alpha", "Fedora 9 Alpha Jigdo" and "Fedora 8 20080204 Re-Spin" === Announcing Fedora 9 Alpha ===

<!-- 1. Gather material from the existing release notes and announcement, ...lpha release today, it’s time for the whole community’s input. Obtain your Alpha live spin here.

== Mini post F-12-Alpha recap == ...on what worked well, and what areas needed improvement for the recent F-12-Alpha release.

| colspan="2" | *K410 is glad that dont need to use F11 alpha | style="color: #407a40" | then I will send out a announcement later - perhaps we can coordinate something with fedora-qa too

* 2010-01-21 - [[Test_Results:Fedora_13_Rawhide_Acceptance_Test_1|Pre-Alpha Rawhide Acceptance Test Plan #1]] * 2010-01-28 - [[Test_Results:Fedora_13_Rawhide_Acceptance_Test_2|Pre-Alpha Rawhide Acceptance Test Plan #2]]