Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 23 Jun 2014 20:46:26 +0000 (UTC)
From: "Bill Havanki (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12676908.1383241739845.31980.1403556386253@arcas>
In-Reply-To: <JIRA.12676908.1383241739845@arcas>
References: <JIRA.12676908.1383241739845@arcas>
Subject: [jira] [Resolved] (ACCUMULO-1834) ReviewBoard guidelines
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ACCUMULO-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bill Havanki resolved ACCUMULO-1834.
------------------------------------

    Resolution: Done

Guidelines are now up on the production site. I included a link in the nav menu and a link from the developer guide. Thanks for all the feedback.

> ReviewBoard guidelines
> ----------------------
>
>                 Key: ACCUMULO-1834
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1834
>             Project: Accumulo
>          Issue Type: Task
>          Components: docs
>            Reporter: Josh Elser
>            Assignee: Bill Havanki
>              Labels: Documentation
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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.2#6252)