On Sun, Dec 1, 2013 at 1:52 PM, Dave Fisher <dave2w...@comcast.net> wrote: > One note I have is I don't think we should be teaching that some of release > steps are "optional" when they are required.
Don't get me wrong -- I would actually prefer to make each PPMC member do the work for each item. The main rationale behind making the checklist items "optional" is something else: to avoid adding yet more design pressure onto the checklist. Making all items "required" means that we have to anticipate all possible edge cases in advance, lest we make it impossible to vote for a release which would otherwise pass but gets hung up on a technicality. How about building in a different safety valve? - Checklist (all items optional, mark only those personally verified): + Checklist (mark only items personally verified; items left unchecked must + be explained in "Notes"): > If we are using the checklist as a way to test and measure the podling for > graduation then I would add the following checkboxes. I don't think we should add any design requirement that does not pertain to voting on the release artifacts. It is already extremely challenging attempting to meet all the absolute requirements being presented by various discussion participants. Marvin Humphrey --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
