Exit Criteria to Production and Release Blocker Nominations

[Null Ack]

Thanks for the comments folks.

Scott thanks for your response, and I certainly do understand the
problems with limited developer resources. If that's really where we
are at in terms of capability I will support what were doing now. I
will only say that the commercial projects I have worked on would
never consider shipping with user visible error messages to production
and would certainly expect them to be flagged as release blockers.
Maybe its something Ubuntu can work towards for the future as
contributors grow.

A compromise could be an additional status for flagging release issues
that detract from a quality user experience that are not considered
release blockers under the current policy, to be ear marked for
resolution as a post production enhancement shortly after release. On
the thinking that atleast some dev resources should be freed-up.

I hope I'm not the only one who considers the current policy dangerous
to the success of Ubuntu - but I'm willing to live with it for now if
thats truly the best our current capability offers.

2009/3/12 Mike Rooney <mrooney at gmail.com>:

> I would agree that a pre-release bug which doesn't exist in a fresh
> Jaunty install should not be a release blocker.

Yes, I agree.

>
> In your perspective, it seems like you want the developers/OS to be a
> service to the testers, and not the other way around.

It's a service to the users, as in my perspective and I hope in others
too, the user experience is what matters most.

> Are we on different pages with anything, or am I misunderstanding your
> views in some way?

I think so, Micheal the point of my email was to present my thoughts
for why the policy of release blocker should be reconsidered.

Regards

Nullack