1: Pre-release binary tarballs to the web.
The binaries are not available to the public until they've been pushed to the mirrors (see step 14). However, they still need to be placed into AFS for the download system to find. If the version of Condor is =X.Y.Z=, then place the binary releases of Condor for the various available architectures into =/p/condor/public/binaries/vX.Y/X.Y.Z=. Note that for any particular architecture, =unstripped= binaries should not be released to the web if there is a corresponding =condordebugsyms= tarball. And with 7.5.x and above, static binaries should not be released.
+*:: WINDOWS: With <Current version +1> hopefully Windows packages will be automatic. People who know how to make Windows packages: TJ, Cathrin, Z, Todd T.
*:: UNIX: Mostly this involves copying everything off of nmi-s006 and into /p/condor/public/binaries/...
*::: Option 1: Use nmi_crowbar
@@ -239,7 +240,6 @@
{endcode}
*:::: (You can also use "=scp nmi-s006:/space/tmp/release-$RELEASE/public/v$RELEASE_MAJOR/'*' ./=" to copy the binaries over. rsync provides the advantage that you can re-run it over and over again if your transfer is interrupted and you won't re-copy what you already have.)
*::: Option 3: Derek has a script to search through a given NMI rundir and move everything we need. The script lives in the nmi_tools directory in git, and is called =move_to_afs=. Beware that this script will eat up around 8 gigabytes while it runs. It's also old and crusty and should be avoided.
-*:: WINDOWS: With <Current version +1> hopefully Windows packages will be automatic. Until that's working, ask Todd Tannenbaum or Ziliang Guo to manually create the packages.
1: Push native packages into the repositories.
1:: Find a machine with at least 3 GB scratch space
