Mailing-List: contact issues-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Mon, 1 Oct 2012 22:31:36 -0500 (CDT)
From: "Brett Porter (JIRA)" <jira@codehaus.org>
To: issues@continuum.apache.org
Message-ID: 
 <494848981.4820.1349148696583.JavaMail.j2ee-jira@codehaus01.managed.contegix.com>
In-Reply-To: 
 <1047157373.58756.1348030641175.JavaMail.j2ee-jira@codehaus01.managed.contegix.com>
Subject: [jira] (CONTINUUM-2687) preparing subsequent releases appends
 timestamp to ID, but never lists them for performing
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


    [ https://jira.codehaus.org/browse/CONTINUUM-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=310123#comment-310123 ] 

Brett Porter commented on CONTINUUM-2687:
-----------------------------------------

A side effect of implementing this is that multiple prepared releases can be stored until they are performed (e.g. to prepare two branches), where before each prepare overwrote the previous one.
                
> preparing subsequent releases appends timestamp to ID, but never lists them for performing
> ------------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2687
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2687
>             Project: Continuum
>          Issue Type: Bug
>            Reporter: Brett Porter
>
> The distributed release manager will append a timestamp to the releaseId of releases if they already exist, but this syntax is not recognised in the server for listing the releases for perform.
> Some consideration to this is needed. Some options:
> # fail a release prepare if an existing one is there
> # warn if you try to prepare a release when one exists, then abandon previous record
> # abandon previous record without warning
> # track multiple prepared releases for a single project
> With the use of the dropdown, it seems that the last was the intent of the UI, but has not really been used in practice. This might be the best approach.
> In addition, it would be valuable to add a "Perform" button to a successful prepare status page so that the step can be skipped.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira