$Id$ Public domain. See http://tug.org/texlive/pkgupdate.html for what information there is on the CTAN-to-TL update process. To add a new architecture: - check that the config.guess output maps to our architecture name (the `platform' routine in TeXLive/TLUtils.pm) - create directory in Master/bin and add at least one file - add lzma and lzmadec binaries in Master/tlpkg/installer - add description in Master/tlpkg/TeXLive/TLUtils.pm - regenerate tlpdb. When switching the release version, the default network directory specified in tl-update-tlnet, TLConfig.pm, and release-texlive-txt. Change those. Then make the new directory, and copy in tlpkg/texlive.tlpdb; tl-update-tlnet will make everything else. But consider mv-ing the old directory so as not to actually make new containers. Coordinate with CTAN. To make the tag + branch of a release after it is complete: svn copy -r 10402 -m'texlive-2008.0 tag based on r10402' svn://tug.org/texlive/trunk svn://tug.org/texlive/tags/texlive-2008.0 svn copy -r 10402 -m'branch2008 branch based on r10402' svn://tug.org/texlive/trunk svn://tug.org/texlive/branches/branch2008 It's the same command, just different destinations. http://svnbook.red-bean.com/en/1.5/svn-book.html#svn.branchmerge Do both a branch and a tag so that it's possible to easily compare the current state of the branch with its starting point (the tag). Different naming convention to branch before a release, for development work before we want to switch trunk over: svn copy -r 12205 -m'texlive-2009-dev tag based on r12205' svn://tug.org/texlive/trunk svn://tug.org/texlive/tags/texlive-2009-dev svn copy -r 12205 -m'branch2009-dev branch based on r12205' svn://tug.org/texlive/trunk svn://tug.org/texlive/branches/branch2009-dev Use -dev instead of .something because - will sort first, keeping the listings in a nice chronological order.