devel-announce September 2014

devel-announce@lists.fedoraproject.org

7 participants
13 discussions

by Jaroslav Reznik

Today at Go/No-Go meeting it was decided to slip Fedora 21 Alpha release by one week due to unresolved blocker bugs [1] and no release candidate available. More details in meeting minutes [2]. As a result, ALL MAJOR MILESTONES, and their dependent tasks, will be pushed out by one week [3]. The next Go/No-Go meeting is on Thursday, Sep 11, the same time at #fedora-meeting-2 channel. [1] http://qa.fedoraproject.org/blockerbugs/milestone/21/alpha/buglist [2] http://meetbot.fedoraproject.org/fedora-meeting-2/2014-09-04/f21_alpha_go... [3] https://fedoraproject.org/wiki/Releases/21/Schedule

9 years, 7 months

1
0
0 / 0

Fedora 21 Alpha Release Readiness Meeting :: Thursday, Sep. 04, 19:00 UTC

by Jaroslav Reznik

Fedora 21 Alpha Release Readiness Meeting. date: 2014-09-04 place: irc.freenode.net in #fedora-meeting-2 time: 19:00 UTC (3 PM EDT, 12 PM PDT, 21:00 CEST) This Thursday, September 04, we will meet to make sure we are coordinated and ready for the Alpha release of Fedora 21 on Tuesday, September 09, 2014. Please note that this meeting will occur on September 04 even if the release is delayed at the Go/No-Go meeting on the same day two hours earlier. You may received this message several times, but I was asked to open this meeting to the teams and I'll also hope this will raise awareness and more team representatives will come to this meeting. This meeting works best when we have representatives from all of the teams. Jaroslav

9 years, 7 months

1
0
0 / 0

Fedora 21 Alpha Go/No-Go Meeting, Thursday, September 04 @ 17:00 UTC

by Jaroslav Reznik

Join us on irc.freenode.net in #fedora-meeting-2 for this important meeting, wherein we shall determine the readiness of the Fedora 21 Alpha. Thursday, September 04, 2014 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST) "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 Candidate (RC) availability and good QA coverage are prerequisites for the Go/No-Go meeting. For more details about this meeting see: https://fedoraproject.org/wiki/Go_No_Go_Meeting In the meantime, keep an eye on the Fedora 21 Alpha Blocker list: http://qa.fedoraproject.org/blockerbugs/milestone/21/alpha/buglist Jaroslav

9 years, 7 months

1
0
0 / 0

← Newer
1
2
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce September 2014