Andras Barna wrote: > yes Then, it resets for them too. The vote reset should be tied to the resubmit button.
The code needs to be stable before voting, and they can always revote quickly if they like. Cheers, Jim > On Fri, May 8, 2009 at 12:27 PM, Jim Walker <James.Walker at sun.com> wrote: >> Dermot McCluskey wrote: >>> Shawn Walker wrote: >>>> Luis de Bethencourt wrote: >>>>> Hey guys, >>>>> >>>>> We have two packages in Source Juicer that have already been voted twice >>>>> positively, they have been promoted to contrib and now the submitter has >>>>> done some fixes and the packages are waiting to be pushed. This is >>>>> something >>>>> that hasn't been clarified in the policy. >>>>> >>>>> My opinion is that the package should be voted twice positively again to >>>>> be promoted. What this means is that the voting counter goes back to zero >>>>> for every resubmission. >>>>> >>>>> Is everybody OK with this? Any thoughts/opinions? >>>> I agree with the voting counter being reset any time the submitter makes >>>> changes to the materials in the submission. >>> Only the submitter? What if an approver changes a file - should that also >>> reset the counter? >> Approvers can change files? >> >> Cheers, >> Jim
