[ http://issues.apache.org/jira/browse/JDO-365?page=comments#action_12414782 ]
Craig Russell commented on JDO-365: ----------------------------------- Oops, try this: The community 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. Trailing <update> and <minor> numbers with zero values are right trimmed, so there might be a 2.0.0.1 or a 2.0.1but not a 2.0.0 or 2.0.1.0. > 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
