On Fri, 4 Nov 2011 09:37:33 -0500 Bruno Wolff III <bruno@xxxxxxxx> wrote: > On Thu, Nov 03, 2011 at 23:17:21 -0700, > Adam Williamson <awilliam@xxxxxxxxxx> wrote: ...snip... > > > Yeah, agreed. I don't think there's any especial need for the > > go/no-go to be an entire day ahead of the release readiness > > meeting, in all honesty - it seems to work fine simply to do it > > earlier the same day. So do you think it'd be alright to suggest > > that as a change for the F17 and beyond scheduling? Every time > > we've decided the delay the go/no-go decision, that choice in > > itself hasn't caused any problems, as far as I'm aware. It simply > > gives us more time for validation, which is never a bad thing... > > I am concerned with the process as executed not matching the > documentation. I'd just like to see a change codified that either > allows moving the Go / No-Go meeting when appropriate or just > schedule it closer to the readiness meeting. I think moving the go/no-go meetings to thursdays and moving the readyness meeting to friday is a fine plan. I think our mirroring is in shape enough to where if we stage things late thursday or friday morning we should be ok. If we do this, next cycle we should NOT do any 'two part' go/no-go meetings. kevin
Attachment:
signature.asc
Description: PGP signature
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
