Every PMC determines their own process and checklist for reviews.
I suspect though, that you're more interested in understanding what we expect projects to do to prepare for a release review. We do have a
checklist, but it's heavily rooted in our history of most of our projects building
Eclipse Platform Plug-ins. If you ignore the bits about bundles and plug-ins, though, it's a pretty good start (further generalizing this checklist is on my to do list).
The EMO does a lot of the actual checking, but we lean on the PMC to assess that the project is working within their scope, is following the rules of the EDP (the open source rules of engagement in particular), and is just generally doing the right sorts of things to develop community. Again, it's up to the PMC to determine how to assess this.
We purposely keep the formality to a minimum. A project team representative asks the PMC for approval of their release and corresponding Release Review materials on the PMC mailing list. The EMO waits for any related discussion to settle; once it's clear that the PMC has given their approval, we move forward with the review.
Once we have the approvals that we require (PMC approval of the release and IP Team approval of the IP Log), we schedule the review. Reviews conclude after one week of being open for community feedback. The date that we assign to a review is the end date of the community feedback period. We schedule those dates on the first and third Wednesdays of every month.
HTH,
Wayne
