-This is a living document that enumerates all the steps necessary to release a new version of Condor.
+This is a living document that enumerates all the steps necessary to release a new version of HTCondor.
In parallel with this effort the wrangler should {wiki: PreparingVersionHistory prepare the version history}
@@ -23,7 +23,7 @@
1: Notify the appropriate people about the update.
*:: For a *stable release* we update the CS pool. Send email to the =uwcs-condor@cs.wisc.edu= list announcing our plans for the pool upgrade. We like to give users at least a few days notice so that if there are important paper deadlines, etc, they have time to finish their jobs, or to let us know they need us to delay the upgrade.
-*:: For a *developer release* we update the NMI pool and CHTC pool. Let the admins of these pools know about the pending release (currently the Condor infrastructure team for NMI, and infrastructure or Dan Bradley for CHTC)
+*:: For a *developer release* we update the NMI pool and CHTC pool. Let the admins of these pools know about the pending release (currently the HTCondor infrastructure team for NMI, and infrastructure or Dan Bradley for CHTC)
1: Make a release branch. The main thing to know is that the branch should have the name =VX_Y_Z-branch=. Here's an example of the steps for a 7.0.3 release, from a known good NMI tag (assuming your working directory is inside of a clone of CONDOR_SRC.git):
*:: The preferred method for making a release branch is from a known good build tag on NMI.
@@ -73,7 +73,7 @@
1: Watch the nightly builds the next morning to ensure everything is working fine.
-1: If you'd like to fire off a build immediately, then read the {wiki: NmiBuild Building Condor with NMI} page. You'll need to start the build as cndrauto so follow the directions.
+1: If you'd like to fire off a build immediately, then read the {wiki: NmiBuild Building HTCondor with NMI} page. You'll need to start the build as cndrauto so follow the directions.
{section: Upgrade the Pools}
@@ -87,7 +87,7 @@
$ nmi_pin --days=365 --force <runid>
{endcode}
This buildid will be unpinned by the *next* wrangler when the *next*
-revision of Condor comes out in this series. Example: If you are the
+revision of HTCondor comes out in this series. Example: If you are the
current release wrangler and have just pinned 7.0.0. The release wrangler
for 7.0.1 will unpin the 7.0.0 release.
@@ -95,7 +95,7 @@
*:: Verify the contents of the .ZIP file
*::: Check the layout of the file (currently there is an extra directory)
*::: Check to see that condor_mail.exe is not missing.
-*::: Check for debug binaries {code}link /dump /imports bin\* | grep -e "MSVC.*D"{endcode} If any of the condor programs or dlls are linked with the debug c-runtime, there will be output. Otherwise there will not be.
+*::: Check for debug binaries {code}link /dump /imports bin\* | grep -e "MSVC.*D"{endcode} If any of the HTCondor programs or dlls are linked with the debug c-runtime, there will be output. Otherwise there will not be.
*:: Either TJ can create the Windows MSI
*:: Rename the zip and MSI file to include the platform string
*:: Test the MSI installer.
@@ -173,7 +173,7 @@
cvs -d /p/condor/repository/HTML co condor-web
cd condor-web/src/downloads
cp v7.3.license.html v7.4.license.html
-edit v7.4.license.html # change the Condor version numebr.
+edit v7.4.license.html # change the HTCondor version numebr.
cvs add v7.4.license.html
cvs ci
cd ../..
@@ -186,7 +186,7 @@
touch licensers-v7.4 problem-v7.4 sendfile-v7.4
{endcode}
-1: Set the release date (the date the new version hit the Condor web site) in the Condor Manual's Version History item devoted
+1: Set the release date (the date the new version hit the HTCondor web site) in the HTCondor Manual's Version History item devoted
to identifying the release date. OR, tell Karen exactly what
date to use, and she'll do it for you. (#1236)
@@ -203,11 +203,11 @@
{endcode}
-{subsection: Release Condor to the world}
+{subsection: Release HTCondor to the world}
-Once you start following these steps, Condor is available to the public.
+Once you start following these steps, HTCondor is available to the public.
1: Release the manual. Move the symlink in /p/condor/public/html/manual for whatever release series you're changing to point at the new version.
{code}
@@ -310,7 +310,7 @@
{subsection: Announce the Release}
-Now the binaries are available for download. Condor is released. However, you need to promptly announce the release as well.
+Now the binaries are available for download. HTCondor is released. However, you need to promptly announce the release as well.
1: Note that following announcements are very generic. For minor bug fixes or features, that's fine. But if there is a major bug fix, a security fix, or a major new feature, call it out in the announcement.
@@ -321,14 +321,14 @@
*::: Here is a sample announcement:
{code}
{ date => 'January 22, 2008',
- title => 'Condor 7.0.0 released!',
+ title => 'HTCondor 7.0.0 released!',
news => <<ENDNEWS
-The Condor Team is pleased to announce the release of
-Condor 7.0.0. This first release in a new stable series
+The HTCondor Team is pleased to announce the release of
+HTCondor 7.0.0. This first release in a new stable series
includes all new features added in the 6.9 development
series. See the
<a href="http://www.cs.wisc.edu/condor/manual/v7.0/8_3Stable_Release.html#sec:New-7-0-0">Version
-History</a> for a complete list of changes. Condor 7.0.0
+History</a> for a complete list of changes. HTCondor 7.0.0
binaries and source code are available from
<a href="http://www.cs.wisc.edu/condor/downloads/">our
Downloads page.</a>
@@ -340,7 +340,7 @@
*:: touch =src/manual/index.html= (so the manual links update with the version information from the =downloads/index.html= page)
*:: NOTE: if you're doing the first release of a new release series, you'll also need to edit:
*::: =src/index.html= to:
-*:::: change the "The Condor Manual:" list of links (chances are good you'll want to remove something older when you add the new one -- we'll never want that list to be longer than 3 links).
+*:::: change the "The HTCondor Manual:" list of links (chances are good you'll want to remove something older when you add the new one -- we'll never want that list to be longer than 3 links).
*::: =src/developers/index.html= to add the new series to the "Manuals and Other Documentation" list.
*::: edit =src/manual/index.html= (to update which versions of each branch/release series are the current manual)
*:: =cvs commit= (all of your changes in condor-web)
@@ -350,10 +350,10 @@
{code}
Hello,
-The Condor Team is pleased to announce the release of Condor 7.0.0. This first
+The HTCondor Team is pleased to announce the release of HTCondor 7.0.0. This first
release in a new stable series includes all new features added in the 6.9
development series. See the Version History for a complete list of changes.
-Condor 7.0.0 binaries and source code are available from our Downloads page.
+HTCondor 7.0.0 binaries and source code are available from our Downloads page.
Version History:
http://www.cs.wisc.edu/condor/manual/v7.0/8_3Stable_Release.html#sec:New-7-0-0
@@ -362,10 +362,10 @@
http://www.cs.wisc.edu/condor/downloads/
-Thank you for your interest in Condor!
+Thank you for your interest in HTCondor!
-- The Condor Team
+- The HTCondor Team
{endcode}
@@ -400,7 +400,7 @@
1: Move unresolved tickets to the next release. ticket-target-mover, documented at ScriptingGitTrac may be assistance.
-1: Update the {link:http://en.wikipedia.org/wiki/Condor_High-Throughput_Computing_System Condor Wikipedia page} to indicate the current release.
+1: Update the {link:http://en.wikipedia.org/wiki/Condor_High-Throughput_Computing_System HTCondor Wikipedia page} to indicate the current release.
1: Stop building the branch nightly by editing this file:
{code}/p/condor/public/html/branches-to-build{endcode}
