English French (fr_FR)
# cd /usr/src/release
# sh generate-release.sh release/9.2.0 /local3/release
# svn co $FSVN/releng/9.2 src
# svn cp $FSVN/releng/9.2 $FSVN/release/9.2.0
# svn cp $FSVN/stable/9@REVISION $FSVN/releng/9.2
# svn log -v $FSVN/stable/9
'''
/stage/cdrom# find . -type f | sed -e 's/^\.\///' | sort > filename.txt
<<extensibility>>
<<future>>
<<lessons-learned>>
<<release-build>>
<<release-proc>>
A set of more stable branches are maintained, known as "FreeBSD-STABLE" or "-STABLE" for short. All branches live in a master Subversion repository maintained by the FreeBSD Project. FreeBSD-CURRENT is the "bleeding-edge" of FreeBSD development where all new changes first enter the system. FreeBSD-STABLE is the development branch from which major releases are made. Changes go into this branch at a different pace, and with the general assumption that they have first gone into FreeBSD-CURRENT and have been thoroughly tested by our user community.
A symlink to [.filename]#../../../ports/arch/packages-X.Y-release#.
A symlink to [.filename]#../../../tools#.
Abstract
Acknowledgements
Additionally, update the "BSD Family Tree" file:
After running these commands, all prepared release files are available in [.filename]#/local3/release/R# directory.
After the quality of the BETA images is satisfying enough, and no large and potentially risky changes are planned, the release branch is created and _Release Candidate_ (RC) images are built from the release branch, instead of the BETA images from the STABLE branch. Also, the freeze on the STABLE branch is lifted and release branch enters a "hard code freeze" where it becomes much harder to justify new changes to the system unless a serious bug-fix or security issue is involved.