Download avr-libc Reference Manual

Transcript
7.6
Release Numbering and Methodology
more than the last stable release.
The patch version number of a development series is always 0 until a new branch is cut
at which point the patch number is changed to 90 to denote the branch is approaching
a release and the date appended to the version to denote that it is still in development.
All versions in development in cvs will also always have the date appended as a fourth
version number. The format of the date will be YYYYMMDD.
So, the development version number will look like this:
1.1.0.20030825
While a pre-release version number on a branch (destined to become either 1.2 or 2.0)
will look like this:
1.1.90.20030828
7.6.2
Releasing AVR Libc
The information in this section is only relevant to AVR Libc developers and can be
ignored by end users.
Note:
In what follows, I assume you know how to use cvs and how to checkout multiple
source trees in a single directory without having them clobber each other. If you
don’t know how to do this, you probably shouldn’t be making releases or cutting
branches.
7.6.2.1
in cvs:
Creating a cvs branch
The following steps should be taken to cut a branch
1. Check out a fresh source tree from cvs HEAD.
2. Update the NEWS file with pending release number and commit to cvs HEAD:
Change ”Changes since avr-libc-<last release>:” to ”Changes in avr-libc<this relelase>:”.
3. Set the branch-point tag (setting <major> and <minor> accordingly):
’cvs tag avr-libc-<major> <minor>-branchpoint’
4. Create the branch:
’cvs tag -b avr-lib-<major> <minor>-branch’
5. Update the package version in configure.in and commit configure.in to cvs
HEAD:
Change minor number to next odd value.
Generated on Fri Apr 23 15:00:23 2004 for avr-libc by Doxygen
122