*:: =V7_0-branch= into =V7_1-branch= (to get all the recent 7.0 changes into 7.1 as well) 1: Make a release branch for the manual. ASK KAREN FIRST! For example, if you're releasing 7.0.3: -*:: =git clone /p/condor/repository/CONDOR_DOC.git= -*:: =cd CONDOR_DOC= -*:: =git branch V7_0_3-branch origin/V7_0-branch= -*:: =git push origin V7_0_3-branch= +{code} +git clone /p/condor/repository/CONDOR_DOC.git +cd CONDOR_DOC +git branch V7_0_3-branch origin/V7_0-branch +git push origin V7_0_3-branch +{endcode} 1: On the main branch of the manual (*not* the newly created release branch, but for example, the regular V7_0-branch), update condor-macros.tex and Makefile to up the version number to the next version, and push those changes to CONDOR_DOC.git. @@ -325,15 +327,19 @@ {endcode} 1: Release the manual. Continuing the V7_0_3 example... -*:: =git clone /p/condor/repository/CONDOR_DOC.git= -*:: =cd CONDOR_DOC= -*:: =git checkout -b V7_0_3-branch origin/V7_0_3-branch= -*:: =cd doc= -*:: =make release= -*:: move the symlink in /p/condor/public/html/manual for whatever release series you're changing to point at the new version. -*::: =cd /p/condor/public/html/manual= -*::: =rm v7.0= -*::: =ln -s v7.0.3 v7.0= +{code} +git clone /p/condor/repository/CONDOR_DOC.git +cd CONDOR_DOC +git checkout -b V7_0_3-branch origin/V7_0_3-branch +cd doc +make release +# move the symlink in /p/condor/public/html/manual +# for whatever release series you're changing to point +# at the new version. +cd /p/condor/public/html/manual +rm v7.0 +ln -s v7.0.3 v7.0 +{endcode} 1: Update the web HTML regarding this release *:: =cvs -d /p/condor/repository/HTML co condor-web=