Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Wed, 23 Oct 2013 21:38:41 +0000 (UTC)
From: "Christopher Tubbs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12649710.1369750669574.113015.1382564321849@arcas>
In-Reply-To: <JIRA.12649710.1369750669574@arcas>
References: <JIRA.12649710.1369750669574@arcas>
Subject: [jira] [Commented] (ACCUMULO-1468) Document release procedures
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Christopher Tubbs commented on ACCUMULO-1468:
---------------------------------------------

As I understand it, the release plugin doesn't do this (http://jira.codehaus.org/browse/SCM-486). I'm not sure we'd want it to anyway. I think it's better to sign a tag with a release version only *after* we've agreed on releasing that commit as that version.

> Document release procedures
> ---------------------------
>
>                 Key: ACCUMULO-1468
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1468
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: docs
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Minor
>             Fix For: 1.6.0
>
>
> Create notes on new release procedures introduced in 1.5.0 to make sure we have more than one person that can create a release candidate.
> I'm thinking the best home might be a new page near the "source code and developer guide" on the CMS.
> Some information that [~ctubbsii] has already provided on the subject: http://mail-archives.apache.org/mod_mbox/accumulo-dev/201305.mbox/raw/%3CCAL5zq9bH8y0FyjXmmfXhWPj8axosn9dZ7%2Bu-R1DK4Y-WM1YoWg%40mail.gmail.com%3E/


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