\hypertarget{release_method_version_info}{}\doxysubsection{Release Version Numbering Scheme}\label{release_method_version_info}
Release numbers consist of three parts, a major number, a minor number, and a revision number, each separated by a dot.

The major number is currently 2, to indicate the multilib layout has been adapted to the fairly different one used starting with A\+V\+R-\/\+G\+CC version 5. Nevertheless, it is still believed to be generally A\+P\+I-\/compatible with release versions 1.\+x.

In the past (up to 1.\+6.\+x), even minor numbers have been used to indicate \char`\"{}stable\char`\"{} releases, and odd minor numbers have been reserved for development branches/versions. As the latter has never really been used, and maintaining a stable branch that eventually became effectively the same as the development version has proven to be just a cumbersome and tedious job, this scheme has given up in early 2010, so starting with 1.\+7.\+0, every minor number will be used. Minor numbers will be bumped upon judgement of the development team, whenever it seems appropriate, but at least in cases where some A\+PI was changed.

Starting with version 1.\+4.\+0, a file $<$\mbox{\hyperlink{version_8h_source}{avr/version.\+h}}$>$ indicates the library version of an installed library tree.\hypertarget{release_method_release_info}{}\doxysubsection{Releasing A\+V\+R Libc}\label{release_method_release_info}
The information in this section is only relevant to A\+VR Libc developers and can be ignored by end users.

\begin{DoxyNote}{Note}
In what follows, I assume you know how to use S\+VN and how to checkout multiple source trees in a single directory without having them clobber each other. If you don\textquotesingle{}t know how to do this, you probably shouldn\textquotesingle{}t be making releases or cutting branches.
\end{DoxyNote}
\hypertarget{release_method_release_branch}{}\doxysubsubsection{Creating an S\+V\+N branch}\label{release_method_release_branch}
The following steps should be taken to cut a branch in S\+VN (assuming \$username is set to your savannah username)\+:


\begin{DoxyEnumerate}
\item Check out a fresh source tree from S\+VN trunk.
\item Update the N\+E\+WS file with pending release number and commit to S\+VN trunk\+:~\newline
 Change {\itshape Changes since avr-\/libc-\/$<$last\+\_\+release$>$\+:} to {\itshape Changes in avr-\/libc-\/$<$this\+\_\+relelase$>$}.
\item Set the branch-\/point tag (setting $<$major$>$ and $<$minor$>$ accordingly)\+:~\newline
 {\ttfamily svn copy svn+ssh\+://\$username@svn.\+savannah.\+nongnu.\+org/avr-\/libc/trunk svn+ssh\+://\$username@svn.\+savannah.\+nongnu.\+org/avr-\/libc/tags/avr-\/libc-\/$<$}{\itshape major}{\ttfamily $>$\+\_\+$<$}{\itshape minor}{\ttfamily $>$-\/branchpoint}
\item Create the branch\+:~\newline
 {\ttfamily svn copy svn+ssh\+://\$username@svn.\+savannah.\+nongnu.\+org/avr-\/libc/trunk svn+ssh\+://\$username@svn.\+savannah.\+nongnu.\+org/avr-\/libc/branches/avr-\/libc-\/$<$}{\itshape major}{\ttfamily $>$\+\_\+$<$}{\itshape minor}{\ttfamily $>$-\/branch}
\item Update the package version in configure.\+ac and commit configure.\+ac to S\+VN trunk\+:~\newline
 Change minor number to next odd value.
\item Update the N\+E\+WS file and commit to S\+VN trunk\+:~\newline
 Add {\itshape Changes since avr-\/libc-\/$<$this\+\_\+release$>$\+:}
\item Check out a new tree for the branch\+:~\newline
 {\ttfamily svn co svn+ssh\+://\$username@svn.\+savannah.\+nongnu.\+org/avr-\/libc/branches/avr-\/libc-\/$<$}{\itshape major}{\ttfamily $>$\+\_\+$<$}{\itshape minor}{\ttfamily $>$-\/branch}
\item Update the package version in configure.\+ac and commit configure.\+ac to S\+VN branch\+:~\newline
 Change the patch number to 90 to denote that this now a branch leading up to a release. Be sure to leave the $<$date$>$ part of the version.
\item Bring the build system up to date by running bootstrap and configure.
\item Perform a \textquotesingle{}make distcheck\textquotesingle{} and make sure it succeeds. This will create the snapshot source tarball. This should be considered the first release candidate.
\item Upload the snapshot tarball to savannah.
\item Update the bug tracker interface on Savannah\+: Bugs ---$>$ Edit field values ---$>$ Release / Fixed Release
\item Announce the branch and the branch tag to the avr-\/libc-\/dev list so other developers can checkout the branch.
\end{DoxyEnumerate}\hypertarget{release_method_release_rolling}{}\doxysubsubsection{Making a release}\label{release_method_release_rolling}
A stable release will only be done on a branch, not from the S\+VN trunk.

The following steps should be taken when making a release\+:


\begin{DoxyEnumerate}
\item Make sure the source tree you are working from is on the correct branch\+:~\newline
 {\ttfamily svn switch svn+ssh\+://\$username@svn.\+savannah.\+nongnu.\+org/avr-\/libc/branches/avr-\/libc-\/$<$}{\itshape major}{\ttfamily $>$\+\_\+$<$}{\itshape minor}{\ttfamily $>$-\/branch}
\item Update the package version in configure.\+ac and commit it to S\+VN.
\item Update the gnu tool chain version requirements in the R\+E\+A\+D\+ME and commit to S\+VN.
\item Update the Change\+Log file to note the release and commit to S\+VN on the branch\+:~\newline
 Add {\itshape Released avr-\/libc-\/$<$this\+\_\+release$>$.}
\item Update the N\+E\+WS file with pending release number and commit to S\+VN\+:~\newline
 Change {\itshape Changes since avr-\/libc-\/$<$last\+\_\+release$>$\+:} to {\itshape Changes in avr-\/libc-\/$<$this\+\_\+relelase$>$\+:}.
\item Bring the build system up to date by running bootstrap and configure.
\item Perform a \textquotesingle{}make distcheck\textquotesingle{} and make sure it succeeds. This will create the source tarball.
\item Tag the release\+:~\newline
 {\ttfamily svn copy . svn+ssh\+://\$username@svn.\+savannah.\+nongnu.\+org/avr-\/libc/tags/avr-\/libc-\/$<$}{\itshape major}{\ttfamily $>$\+\_\+$<$}{\itshape minor}{\ttfamily $>$\+\_\+$<$}{\itshape patch}{\ttfamily $>$-\/release}~\newline
 or~\newline
 {\ttfamily svn copy svn+ssh\+://\$username@svn.\+savannah.\+nongnu.\+org/avr-\/libc/branches/avr-\/libc-\/$<$}{\itshape major}{\ttfamily $>$\+\_\+$<$}{\itshape minor}{\ttfamily $>$-\/branch svn+ssh\+://\$username@svn.\+savannah.\+nongnu.\+org/avr-\/libc/tags/avr-\/libc-\/$<$}{\itshape major}{\ttfamily $>$\+\_\+$<$}{\itshape minor}{\ttfamily $>$\+\_\+$<$}{\itshape patch}{\ttfamily $>$-\/release}
\item Upload the tarball to savannah.
\item Update the N\+E\+WS file, and commit to S\+VN\+:~\newline
 Add {\itshape Changes since avr-\/libc-\/$<$major$>$\+\_\+$<$minor$>$\+\_\+$<$patch$>$\+:}
\item Update the bug tracker interface on Savannah\+: Bugs ---$>$ Edit field values ---$>$ Release / Fixed Release
\item Generate the latest documentation and upload to savannah.
\item Announce the release.
\end{DoxyEnumerate}

The following hypothetical diagram should help clarify version and branch relationships.

 
\begin{DoxyImage}
\includegraphics[width=5in]{}
\doxyfigcaption{Release tree}
\end{DoxyImage}
 