[
https://issues.apache.org/jira/browse/DERBY-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13638012#comment-13638012
]
Rick Hillegas commented on DERBY-6190:
--------------------------------------
Thanks for raising this topic, Dag. The Derby version scheme is described here:
http://db.apache.org/derby/papers/versionupgrade.html. I don't understand why
we need to support a distinction between alpha and beta distributions. Over the
last eight years, I have only seen a need for two kinds of distributions:
o Releases - These fully support upgrade. You can upgrade to and from a release.
o Snapshots - These don't support upgrade. You can't upgrade to them and you
can't upgrade from them. Snapshots are purely experimental.
I think that the beta flag is sufficient to distinguish releases from
snapshots. I would support removing the peculiar convention that fixpack 0
without the beta flag means the distribution is alpha. It confuses new release
managers.
Can anyone explain the original purpose of the distinction between alpha and
beta? Thanks.
> 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
