----- Original Message -----
On Mon, Nov 11, 2013 at 06:56:57 -0500,
Jaroslav Reznik <jreznik(a)redhat.com> wrote:
>I'd say the Go/No-Go should be the break point to release/not to release as
>for primary offering. It could be a part of the Go/No-Go meeting to state
>release readiness of all deliverables we have (based on the sign offs or
>directly in the meeting?).
For consistancy and blame I think that is a good idea. Dennis shouldn't
feel the heat for when screw ups result in a spin being dropped. Having
it done at that point also keeps people from hoping for some float to
get the sign off done.
>Do we have anything as
>for marking tests passed or just
I don't think so.
>I'm not going to comment what's written bellow, I think Dennis covered it
>pretty well. I'm sorry if I missed the spis process, I know it was happening
>and now I know it's enforced - so let's try to find the way how to put it
>into schedule, communicate it better. It's definitely worth having it, and
>be more than happy to help with it!
This policy is change is something that should have been communicated to you,
so there is blame to go around. I could have thought of doing that since
I see enough to have been able to draw the conclusion that this is something
that should have been on the spins schedule.
Current spins schedule is at , is the rest of tasks still valid? I'm going
to add sign off there too.