$TenDRA: book.xml 2447 2006-03-23
21:15:51Z verm $
Copyright © 2004, 2005, 2006 TenDRA Documentation Team
Berkeley Systems Design License
Redistribution and use in source (SGML DocBook) and 'compiled' forms (SGML, HTML, PDF, PostScript, RTF and so forth) with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code (SGML DocBook) must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified.
Redistributions in compiled form (transformed to other DTDs, converted to PDF, PostScript, RTF and other formats) must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS DOCUMENTATION IS PROVIDED BY THE TENDRA DOCUMENTATION TEAM "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE TENDRA DOCUMENTATION TEAM BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This document was generated on 2006-09-07 16:04:39
Abstract
This is the TenDRA release checklist.
Please email us at <docs@ten15.org> if you see any errors or
omissions.
Table of Contents
This document describes the various procedures and actions which must be taken to facilitate a TenDRA release. It has been created in the interest of consistency and yadda yadda yadda across releases.
Freeze source tree 30 days before anticipated release. Only commit bug fixes, documentation updates, minor changes and potentially previously discussed changes.
Send heads-up message to tendra-dev@ten15.org.
Create the release branch.
cvs ...
cvs ...
Run the regression suites on the release branch.
test ...
test ...
Bump the version number in these files:
filename1
filename2
Tag the branch.
cvs ...
cvs ...
Roll the necessary tarballs and move them to the appropriate directories.
somescript.sh
anotherscripttocheck.sh
Allow 48 hours to synchroznize mirrors.
Send message to mirrors@ten15.org.
Run checkscript.sh to ensure all mirrors are up-to-date.
Announce release on announce@ten15.org.
URL to release announcement template (changes, enhancements, fixes, etc.)
Various documents that will be shipped with releases of TenDRA must be compiled from their SGML source into text form. These include:
README
CONTRIBUTORS
TEAM
FAQ
The release script will handle rebuilding of the man pages to reflect the version change. The CVS repository will always contain man pages that hold the CVS tag, to alleviate any confusion.