Done. I added a sentence defining “carrying” as “oversight”. On Dec 9, 2014, at 2:18 AM, Alex Harui <aha...@adobe.com> wrote:
> Maybe I’m being too picky, but the vote proposal said: "I suggest that at > any point in the release process a vote should be carried over if the > person voting indicates they wish the vote should carry over.” > > The current wiki version says: "The release manager can carry over of > votes from previous release candidates to the new release candidate if > changes between release candidates contain no code changes or changes to > legally significant documents.” > > I would suggest either removing that section entirely and hoping we always > have enough folks willing to re-check, or re-wording to: “If a PMC member > voted on a release candidate, and the release manager creates a new one, > the PMC member can state that they want their vote to be carried over”. > > And I would suggest moving that point below the one that says that you > don’t have to re-check everything (since re-checking changes is preferred). > > I wouldn't put any qualifications on what changes do or don’t qualify for > carryover. I trust each PMC member to be a good judge of when a carryover > is proper, and we can avoid later arguments on what constitutes a code > change. > > -Alex > > On 12/8/14, 2:18 PM, "Harbs" <harbs.li...@gmail.com> wrote: > >> I don’t see my last two emails in the archives. Sorry if this is going >> out more than once… >> >> Here is a link to the modified wiki.[1] I think the changes are pretty >> minor… I removed mention of carried votes from the voting timeframe >> section, and clarified the wording in the “Product Release” section. >> >> Harbs >> >> [1]https://cwiki.apache.org/confluence/display/FLEX/Guidelines >> >
