[Test-Announce] Fedora 13 Alpha Go/No-Go Meeting RESCHEDULED: 2010-02-25 @ 19:00 UTC (14:00 EST)

[Adam Williamson]

IMPORTANT NOTE: we are rescheduling the Go/No-Go meeting for Fedora 13
Alpha. Previously scheduled for 2010-02-25 01:00 UTC, it is now
scheduled for 2010-02-25 19:00 UTC (14:00 EST, 11:00 PST). This delay is
to give sufficient time for the QA team to test the expected RC3 build.

The original announcement, with the new time, is reproduced below for
reference.

Join us on irc.freenode.net #fedora-meeting for this important meeting.
Thursday, February 25, 2010 @ 19:00 UTC (14:00 EST).

"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 important meeting see: 
https://fedoraproject.org/wiki/Engineering_Readiness_Meetings
-- 
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

Fedora 13 Alpha Go/No-Go Meeting RESCHEDULED: 2010-02-25 @ 19:00 UTC (14:00 EST)

[Till Maas]

On Wed, Feb 24, 2010 at 01:57:02PM -0800, Adam Williamson wrote:
>  IMPORTANT NOTE: we are rescheduling the Go/No-Go meeting for Fedora
> 13 
>  For more details about this important meeting see: 
>  https://fedoraproject.org/wiki/Engineering_Readiness_Meetings 
IMHO it would help a lot if there weren't always at least two names for
every event or task.

E.g. on
http://poelstra.fedorapeople.org/schedules/f-13/f-13-all-tasks.html
there are the
"Alpha Go/No-Go Meeting (20:00 EST)" and the "Alpha Project Wide Release
Readiness Meeting"
Now also using "Engineering Readiness Meetings" is very easy to confuse
with the other meeting, especially because both happen within
about 24 hours or not.

Regards
Till

F-13-Alpha Go/No-Go 2010-02-25 @ 19:00 UTC - Meeting Recap

[James Laska]

=========================================================
#fedora-meeting: F-13-Alpha engineering readiness meeting
=========================================================


Meeting started by jlaska at 18:59:18 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2010-02-25/fedora-meeting...
.



Meeting summary
---------------
* gathering devel, rel-eng and qa reps  (jlaska, 18:59:40)

* intro  (jlaska, 19:06:24)
  * The purpose is to decide whether the alpha has met the release
    criteria  (jlaska, 19:07:38)
  * LINK:
    https://fedoraproject.org/wiki/Fedora_13_Alpha_Release_Criteria
    (jlaska, 19:07:56)

* Go or No Go  (jlaska, 19:09:02)
  * traditional x86-64 install is broken (bug#568235)  (jlaska,
    19:11:39)
  * live install is broken (bug#565840)  (jlaska, 19:11:44)
  * installing updates is broken (bug#568193 bug#567346)  (jlaska,
    19:12:12)
  * QA votes 'no go' - citing additional testing against remaining
    F13Alpha blockers and walking the Alpha test matrix  (jlaska,
    19:31:42)
  * Rel-Eng votes 'no go' - reluctant considering how close we are and
    that the next RC will likely be the final  (jlaska, 19:32:28)
  * Devel votes 'no go' - notting cited the current data and matrix
    results, dcbw cited importance of installing  (jlaska, 19:34:26)

* contingency plan  (jlaska, 19:41:15)
  *
    https://fedoraproject.org/wiki/Engineering_Readiness_Meetings#Contingency...
    indicates a 1 week slip as a contingency plan  (jlaska, 19:41:35)
  * Oxf13 notes that with No Frozen Rawhide (NFR), we no longer have the
    pressure valves from previous releases.  Developing (rawhide) and
    testing (f-13-updates-testing) can continue  (jlaska, 19:52:32)
  * IDEA: Do not slip Beta/Final milestone dates, due to NFR not
    shorting developers on development time.  (Oxf13, 19:53:26)
  * AGREED: decided to absorb the slip and not move the F-13 release out
    by one week (future slips may incur a cost)  (jlaska, 19:58:30)
  * ACTION: Oxf13 will announce the slip to (devel-)announce  (Oxf13,
    19:59:50)
  * ACTION: stickster will update schedule pages and poke poelcat about
    TJ  (Oxf13, 20:00:42)
  * ACTION: stickster will re-schedule release readiness meeting
    (Oxf13, 20:01:25)
  * ACTION: QA - continue testing RC4 when available and verifying
    remaining F13Alpha bugs  (jlaska, 20:04:04)

Meeting ended at 20:05:09 UTC.




Action Items
------------
* Oxf13 will announce the slip to (devel-)announce
* stickster will update schedule pages and poke poelcat about TJ
* stickster will re-schedule release readiness meeting
* QA - continue testing RC4 when available and verifying remaining
  F13Alpha bugs




Action Items, by person
-----------------------
* Oxf13
  * Oxf13 will announce the slip to (devel-)announce
* stickster
  * stickster will update schedule pages and poke poelcat about TJ
  * stickster will re-schedule release readiness meeting
* **UNASSIGNED**
  * QA - continue testing RC4 when available and verifying remaining
    F13Alpha bugs




People Present (lines said)
---------------------------
* jlaska (102)
* Oxf13 (86)
* stickster (39)
* adamw (24)
* ajax (7)
* dlehman (5)
* zodbot (5)
* dcbw (4)
* notting (3)
* nirik (2)
* clumens (1)
* mchua (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot