On Mon, Sep 15, 2008 at 19:59, Brad Nicholes <[EMAIL PROTECTED]> wrote:
> In general, I am on board with this as you outlined it.  Let me make a
> couple more suggestions (inline)

Thanks for the comments.  A few things I thought of after sending the
1st email are also below.


>> Suggestion 2)  Don't mess with other people's votes.
>>
>
> +1, even when a proposal is modified, the existing votes need to
> remain.  However we do need to somehow put a procedure in place that
> allows for a re-review.  I don't have any suggestions for that yet.

Perhaps an SVN commit that does nothing but remove *all* votes for a
given stanza, and make sure the log entry indicates what is going on?
Alternately, if a proposal is reworked, and needs re-review, add that
to the notes about the backport.  That's...cumbersome, but I can't
think of a better idea.




>> Suggestion 4)  When a backport has been accepted, move the entire
>> stanza into a CHANGES file (or something similar), along with a date
>> stamp..  This should be done when the changes are actually committed
>> to that branch, not when the votes are cast.  This also means that a
>> CHANGES file needs to be created.
>>
>
> +1 again, another suggestion would be to just move the stanza to lower
> section with the same STATUS file.  But I am good with this either way.

I think that I prefer moving them to another file, for two reasons:
1)  It keeps the STATUS file from growing without bound.
2)  the Revision diffs should be very obvious as to what is happening,
what with a big chunk of text removed from STATUS, and appearing in
CHANGES.




-- 
Jesse Becker
GPG Fingerprint -- BD00 7AA4 4483 AFCC 82D0 2720 0083 0931 9A2B 06A2

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers

Reply via email to