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.
+*:: WINDOWS: With <Current version +1> hopefully Windows packages will be automatic. If you have only the tarballs and not the Windows MSI/ZIP, you can build them from the tarballs. People who know how to make Windows packages: TJ, Cathrin, Z, Todd T.
+1::: Unzip/untar the windows tarball into a working directory, c:\scratch\temp for instance. You will end up with all of the files in c:\scratch\temp\public
+1::: Create a directory for the packagages, c:\scratch\temp\package for instance.
+1::: Set your git repository to the branch that you are releasing and make sure that it doesn't have any extraneous files.
+{code}
+> cd CONDOR_SRC\msconfig
+> dopackaging c:\scratch\temp\public c:\scratch\temp\package
+{endcode}
+this will make the .msi and .zip for Windows in the c:\scratch\temp\package directory.
+
*:: UNIX: Mostly this involves copying everything off of nmi-s006 and into /p/condor/public/binaries/...
*::: Option 1: Use nmi_crowbar
