[llvm-dev] Formalize "revert for more design review" policy.

[Nicolai Hähnle via llvm-dev]

Just in case somebody misses it, the thread that you're necro-ing here
is 4 years old.

Cheers,
Nicolai

On Fri, Oct 23, 2020 at 1:38 AM Mehdi AMINI via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> It seems like there was a general agreement in this thread, and our current written guidelines say "In addition, if substantial problems are identified, it is expected that the patch is reverted and fixed offline", which may not be explicit enough.
>
> With the previous suggestions from Philip's incorporated in Sean's proposal, I amended the doc here: https://reviews.llvm.org/D89995
>
> Thanks,
>
> --
> Mehdi
>
>
>
>
>
> On Fri, Mar 11, 2016 at 7:46 AM Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>
>> I agree with the paragraph, and most of the comments thereafter. The
>> intention to clarify reverts as an evolutionary process instead of a
>> punishment is most welcome.
>>
>> Without reverts we can't have post-commit reviews in any way,
>> especially with so many downstream projects depending on LLVM.
>>
>> Code and bot owners may be more trigger happy than other members, but
>> that's because they care about the overall status of their part in the
>> compiler and/or their architectures, and that's an important point of
>> view that should not be taken lightly.
>>
>> I believe our community works mostly well in regards to commits,
>> reviews and reverts, but it's good to encode at least the general idea
>> so that new members don't feel bad about having their patches
>> reverted.
>>
>> cheers,
>> -renato
>>
>> On 9 March 2016 at 12:00, Sean Silva via llvm-dev
>> <llvm-dev at lists.llvm.org> wrote:
>> > Recently there's been some friction over reversions (I can remember two
>> > cases in recent memory). In both issues the general feel I got is that as a
>> > community we should honor "revert for more design review" requests
>> > unconditionally.
>> >
>> > What do you guys think of adding something like this to DeveloperPolicy.rst
>> > as an item at the end of the numbered list in
>> > http://llvm.org/docs/DeveloperPolicy.html#code-reviews ?
>> >
>> > #. Sometimes patches get committed that need more discussion.
>> >    If a developer thinks that a patch would benefit from some more review
>> >    and promptly communicates this, the patch should be reverted (preferably
>> >    by the original author, unless they are unresponsive).
>> >    Developers often disagree, and erring on the side of the developer
>> >    asking for more review prevents any lingering disagreement over code in
>> >    the tree.
>> >
>> > "promptly" is there mostly to avoid suggesting a "necro-revert"; once the
>> > code has been in tree for long enough at some point it would be more
>> > appropriate to open a bug report or start a fresh discussion.
>> >
>> > "unresponsive" add some nebulousness, but I think it's an important
>> > exception to call out for the "preferably by the original author".
>> >
>> > -- Sean Silva
>> >
>> > _______________________________________________
>> > LLVM Developers mailing list
>> > llvm-dev at lists.llvm.org
>> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>> >
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev



-- 
Lerne, wie die Welt wirklich ist,
aber vergiss niemals, wie sie sein sollte.