db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Russell (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JDO-365) Create web page with instructions for creating a release
Date Sun, 04 Jun 2006 20:38:30 GMT
     [ http://issues.apache.org/jira/browse/JDO-365?page=all ]

Craig Russell updated JDO-365:

    Attachment: HowToReleaseJDO.txt

I've added some text to describe the release numbering scheme. Comments?

The release manager first decides on the name of the release. The format
of the name is <spec-number>.<major>.<minor>.<update>. 
The spec-number is either 1 for JDO 1 or 2 for JDO 2. The major number might change for
a new JSR. The minor number would change for a specification revision
approved by the JCP via specification maintenance review. The update number
can be used for changes that do not need a maintenance review and do
not change the interfaces.

Interim releases prior to final release are identified by a suffix on the
release number. Common suffixes include: -alpha, -beta, -beta2, -rc1, -rc2.
Generally, the suffixes are part of the release plan, and the contents
of each suffix release are agreed by the community. There might be
significant changes in functionality between the suffix releases. Each
suffix release goes through the process documented here.

> Create web page with instructions for creating a release
> --------------------------------------------------------
>          Key: JDO-365
>          URL: http://issues.apache.org/jira/browse/JDO-365
>      Project: JDO
>         Type: Task

>   Components: site and infrastructure
>     Reporter: Michelle Caisse
>     Assignee: Craig Russell
>  Attachments: HowToReleaseJDO.txt, HowToReleaseJDO.txt, HowToReleaseJDO.txt, HowToReleaseJDO.txt,
HowToReleaseJDOmc.txt, HowToReleaseJDOmc.txt, sign-directory
> Make information about how to do a release available to the community so that release
manager responsibility can be shared.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message