Re: No answers on CommitFest procedures?

Pavan,

> I think we should. For example, one of the WIP patches is submitted by
> me. One reason I marked it WIP because I was not sure what is
> considered as WIP and what is not. The patch is ready for review, but
> of course have some open items and may need further work once I
> receive the feedback. But I can not make progress either before the
> current work is reviewed, either at the code level or design level. I
> expect that feedback during this commit fest.

I guess the problem I'm having is that people are using various statuses,
but there's no clear indication what they mean. Currently on the
commitfest we have:

Pending Review
WIP
Waiting on Response
Proof of Concept

And for the non-committer reviewers, we'll probably need "Ready for
Committer" as well. I thing we need to restrict the list of statuses to a
coherent list, and have definitions for each.

--
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco