#fedora-meeting-2: F19 Beta Go/No-Go meeting
Meeting started by jreznik at 17:01:06 UTC
(full logs).
Meeting summary
- Roll Call (jreznik, 17:01:33)
- Purpose of this meeting (jreznik, 17:04:42)
- Purpose of this meeting is to see whether or
not F19 Beta is ready for shipment, according to the release
criteria. (jreznik,
17:04:44)
- This is determined in a few ways: (jreznik,
17:04:46)
- No remaining blocker bugs (jreznik,
17:04:47)
- Test matrices for Beta are fully
completed (jreznik,
17:04:49)
- http://qa.fedoraproject.org/blockerbugs/milestone/19/beta/buglist
(jreznik,
17:04:50)
- https://fedoraproject.org/wiki/Test_Results:Fedora_19_Beta_RC4_Install
(jreznik,
17:04:52)
- https://fedoraproject.org/wiki/Test_Results:Fedora_19_Beta_RC4_Base
(jreznik,
17:04:53)
- https://fedoraproject.org/wiki/Test_Results:Fedora_19_Beta_RC4_Desktop
(jreznik,
17:04:55)
- https://fedoraproject.org/wiki/Fedora_19_Beta_Release_Criteria
(jreznik,
17:04:56)
- blocker review (jreznik, 17:05:54)
- Up for review today, we have: (tflink,
17:06:02)
- 4 Proposed Blockers (tflink,
17:06:10)
- 2 Accepted Blockers (tflink,
17:06:10)
- (959677) IndexError: list index out of range (tflink, 17:06:32)
- https://bugzilla.redhat.com/show_bug.cgi?id=959677
(tflink,
17:06:33)
- Proposed Blocker, anaconda, NEW (tflink,
17:06:33)
- AGREED: 959677 -
RejectedBlocker - While this is not good, it is limited to a
specific type of install media and a specific action within the
installer UI that users are not likely to do. Rebooting at that
point in the install does not cause data loss and thus this is
deemed to not be a blocker for F19 beta (tflink,
17:09:53)
- (966598) Crash in VG creation when installing LVM-on-Intel firmware RAID (19 Beta RC4) (tflink, 17:10:06)
- https://bugzilla.redhat.com/show_bug.cgi?id=966598
(tflink,
17:10:09)
- Proposed Blocker, anaconda, NEW (tflink,
17:10:12)
- AGREED: 966598 -
RejectedBlocker - This does cause problems during install but it is
limited to specific cases of re-using disks that have existing
metadata from old installs. As such, it is too much of a corner case
to block release and is rejected as a blocker for F19 beta
(tflink,
17:15:49)
- (966586) System doesn't boot after upgrade on UEFI (tflink, 17:15:59)
- https://bugzilla.redhat.com/show_bug.cgi?id=966586
(tflink,
17:15:59)
- Proposed Blocker, fedup, NEW (tflink,
17:15:59)
- AGREED: 966586 -
RejectedBlocker - While this does have a negative impact on upgrades
for UEFI systems, it is workaround-able and doesn't result in a
system which can't be reasonably fixed. An updated grub2 package
should fix this but even if it doesn't, the workarounds will be
documented. Rejected as a release blocking bug for F19 beta.
(tflink,
17:28:55)
- (957783) fedup from F18 -> F19 hangs at reboot (tflink, 17:29:06)
- https://bugzilla.redhat.com/show_bug.cgi?id=957783
(tflink,
17:29:06)
- Proposed Blocker, systemd, NEW (tflink,
17:29:06)
- AGREED: 957783 -
RejectedBlocker - While this is a nasty looking bug, it does not
actually interfere with the upgrade process beyond requiring a
manual reboot post-upgrade. As such, it was judged not to be severe
enough to block release and is rejected as a release blocking bug
for F19 beta. (tflink,
17:33:41)
- (964069) Anaconda creates native partition in text mode if LVM or btrfs is selected (tflink, 17:35:25)
- https://bugzilla.redhat.com/show_bug.cgi?id=964069
(tflink,
17:35:25)
- Accepted Blocker, anaconda, VERIFIED
(tflink,
17:35:25)
- 964069 was confirmed as fixed with F19 beta
RC3 (tflink,
17:36:54)
- (966162) fedora-dmraid-activate shouldn't tell kpartx to use a partition delimiter (tflink, 17:38:32)
- https://bugzilla.redhat.com/show_bug.cgi?id=966162
(tflink,
17:38:35)
- Accepted Blocker, dmraid, VERIFIED (tflink,
17:38:37)
- 966162 was verified as fixed in F19 beta
RC4 (tflink,
17:39:31)
- after blocker bug review, there are no accepted
& unresolved blocker bugs (jreznik,
17:41:36)
- Test matrices coverage (jreznik, 17:42:08)
- test matrices coverage is ok (jreznik,
17:44:04)
- every alpha/beta test is covered for at least
one arch, only couple of safe ones were pulled from previous test
runs (jreznik,
17:45:25)
- Go/No-Go decision (jreznik, 17:45:38)
- per QA's policy, as there are no accepted
unaddressed blockers and test coverage is sufficient, QA votes
"go" (jreznik,
17:47:55)
- based on the blocker bugs status and test
matrices coverage, Fedora Program Manager votes "go" (jreznik,
17:48:11)
- AGREED: Fedora 19
Beta is +1 to go by Fedora QA, FPL, FPGM and developers (jreznik,
17:50:32)
- open floor (jreznik, 17:51:58)
Meeting ended at 17:59:19 UTC
(full logs).
Action items
- (none)
People present (lines said)
- tflink (80)
- jreznik (71)
- adamw (70)
- Viking-Ice (18)
- nirik (15)
- rbergeron (7)
- zodbot (4)
- satellit (1)
Generated by MeetBot 0.1.4.