devel-announce April 2015

devel-announce@lists.fedoraproject.org

6 participants
13 discussions

Fedora 22 Beta Go/No-Go Meeting, Thursday, April 09 @ 17:00 UTC
by Jaroslav Reznik 07 Apr '15

07 Apr '15

Join us on irc.freenode.net in #fedora-meeting-2 for this important meeting, wherein we shall determine the readiness of the Fedora 22 Beta. Thursday, April 09, 2015 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. We don't have RC yet, the list of blocker bugs does not look so scary now but there's still quite a lot of work ahead of us. If you have any bug on the list, please help us with Beta release. If we won't be ready by Thursday, we will use this meeting to review blockers and decide what to do next. For more details about this meeting see: https://fedoraproject.org/wiki/Go_No_Go_Meeting In the meantime, keep an eye on the Fedora 22 Beta Blocker list: http://qa.fedoraproject.org/blockerbugs/milestone/22/beta/buglist Jaroslav

1 0

Fedora 22 Beta Release Readiness Meeting :: Thursday, April 09, 19:00 UTC
by Jaroslav Reznik 07 Apr '15

07 Apr '15

Fedora 22 Beta Release Readiness Meeting. date: 2015-04-09 place: irc.freenode.net in #fedora-meeting-2 time: 19:00 UTC (3 PM EDT, 12 noon PDT, 21:00 CEST) This Thursday, April 09, we will meet to make sure we are coordinated and ready for the Beta release of Fedora 22 on Tuesday, April 14, 2015. Please note that this meeting will occur on April 09 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. We also have a badge! Jaroslav

1 0

Fedora 22 Beta Freeze
by Dennis Gilmore 02 Apr '15

02 Apr '15

Hi all, Tuesday was an important day on the Fedora 22 schedule[1], with two significant cut-offs. Tuesday was the Beta freeze[2]. This means that only packages which fix accepted blocker or freeze exception bugs[3][4] will be marked as 'stable' and included in the Beta composes. Other builds will remain in updates-testing until the Beta release is approved, at which point the Beta freeze is lifted and packages can move to 'stable' as usual until the Final freeze. Finally, Tuesday was the '100% code complete deadline' Change Checkpoint[8], meaning that Fedora 22 Changes must now be ' New accepted changes must be code complete, meaning all the code required to enable to the new change is finished. The level of code completeness is reflected as tracker bug state ON_QA. The change does not have to be fully tested by this deadline'. Regards Dennis [1] https://fedoraproject.org/wiki/Releases/22/Schedule [2] https://fedoraproject.org/wiki/Milestone_freezes [5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [8] https://fedoraproject.org/wiki/Changes/Policy

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce April 2015