accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1834) ReviewBoard guidelines
Date Sat, 02 Nov 2013 23:47:17 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812220#comment-13812220
] 

Christopher Tubbs commented on ACCUMULO-1834:
---------------------------------------------

CTR says reviews aren't required for a commit, but it doesn't rule it out as an option. In
these cases (such as an anticipated concern about the readiness or quality of a feature implementation),
it seems like a formal vote is still an option. To exercise that option, it seems to me that
the formal voting should take place on the mailing list, just like other votes, not in ReviewBoard.
ReviewBoard feedback can, of course, be used to inform a committer's decision to call a formal
vote.

> ReviewBoard guidelines
> ----------------------
>
>                 Key: ACCUMULO-1834
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1834
>             Project: Accumulo
>          Issue Type: Task
>          Components: docs
>            Reporter: Josh Elser
>              Labels: Documentation
>             Fix For: 1.6.0
>
>
> We currently don't have any guidelines on how we should be using reviewboard.
> For example -- How many "ship it"'s are needed to merit consensus? How do we make sure
that reviews get applied after consensus is reached?
> Figure out what to do and then write it down.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message