Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 20 May 2013 12:33:16 +0000 (UTC)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12643862.1366599531244.346368.1369053196103@arcas>
In-Reply-To: <JIRA.12643862.1366599531244@arcas>
References: <JIRA.12643862.1366599531244@arcas>
Subject: [jira] [Commented] (DERBY-6190) Remove unused alpha versioning code
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rick Hillegas commented on DERBY-6190:
--------------------------------------

Thanks, Dag. Or we could dispense with both the "alpha" and "beta" terms. For me, the words "alpha" and "beta" refer to milestones in the testing of a program. The snapshots are more raw than alpha-tested code. Snapshots haven't even been integration-tested and might not even have been unit-tested. If we are going to change the terminology, then I'd prefer that we settle on a word which captures the experimental, buggy nature of snapshots. Note the following lifecycle:

o During development, we add new features to the trunk. All distributions cut from the trunk are raw and experimental.

o Shortly after creating a release branch, the release manager turns off the alpha/beta/snapshot bit. Every distribution cut from a release branch is a release candidate.

I agree that "snapshot" is the wrong word too. In the Apache world, a snapshot could just be a release candidate which the community has barely vetted. Maybe the right distinction is "production" vs "development" or "production" vs "experimental". Any release candidate cut from a release branch can boot a production database. A distribution cut from the trunk can't: it's experimental code which is fit only for development use.

Thanks,
-Rick
                
> Remove unused alpha versioning code
> -----------------------------------
>
>                 Key: DERBY-6190
>                 URL: https://issues.apache.org/jira/browse/DERBY-6190
>             Project: Derby
>          Issue Type: Improvement
>          Components: Network Client, Services
>            Reporter: Dag H. Wanvik
>
> I believe we no longer use the alpha versioning code, only the beta one. I suggest removing the unused alpha versioning code.

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