-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/20/2015 07:16 AM, Kamil Paral wrote: >> The biggest issue is this, I think. We probably need to encode >> "Special Blockers" into the Go/No-Go process. I don't think that >> assurance that it will be fixed on time is necessarily good >> enough. Particularly given the time that it takes stable updates >> to make it to the mirrors, I'd say that we probably want to say >> that any such special blockers have to be queued for stable >> before the Go/No-Go decision is made. (This may in some cases >> mean *during* the Go/No-Go meeting, of course.) > > Well, here's our latest mess-up: > https://bodhi.fedoraproject.org/updates/FEDORA-2015-e00b75e39f > dnf-plugin-system-upgrade-0.7.0-1.fc22 had enough karma for stable > on Oct 29, which was Go/No-Go day. Therefore it was considered "resolved". "Had enough karma" != queued for stable. When I say "queued for stable", I mean that it needs to be "submitted for stable" and awaiting a push (if not already pushed). According to the history on that bug, it was not actually submitted for stable until November 2nd. That would have failed my criterion above, since that was after Go/No-Go. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlZPNJ8ACgkQeiVVYja6o6Oj9QCdFAiaD/vZKsG5PKBAL9lpb1l4 eAsAoIGAep7Y/GLy2GKD1V6p+K3QFWDW =jNKy -----END PGP SIGNATURE----- -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
