update run.bat to point to pmd-1.0rc2.jar
update cpdgui.bat to point to pmd-1.0rc2.jar
update build.xml to reflect pmd-1.0rc2
update xdocs/running.xml to reflect pmd-1.0rc2
update the release date in the changelog
move rules from "newrules.xml" into a real ruleset file
update release number in project.xml

set ANT_HOME=c:\ant
ant dist
ant test
Do all the JUnit tests run?  OK, then:
ant dist

TESTS: Can you
1) run 1 file and get a report
run c:\data\pmd\pmd\test-data\Unused1.java xml rulesets/unusedcode.xml
run c:\data\pmd\pmd\test-data\Unused1.java html rulesets/unusedcode.xml
2) run the Ant 'pmd' task and get a report
ant pmd

Prepare binary release:
rmdir /q /s c:\tmp\pmd
mkdir -p c:\tmp\pmd\etc
mkdir c:\tmp\pmd\lib
mkdir -p c:\tmp\pmd\docs\javadoc
copy run.bat c:\tmp\pmd\etc
copy build.xml c:\tmp\pmd\etc
copy cpdgui.bat c:\tmp\pmd\etc
copy readme.txt c:\tmp\pmd\etc
copy changelog.txt c:\tmp\pmd\etc
copy ..\lib\pmd-1.0rc2.jar c:\tmp\pmd\lib
copy ..\lib\xmlParserAPIs-2.0.2.jar c:\tmp\pmd\lib
copy ..\lib\xercesImpl-2.0.2.jar c:\tmp\pmd\lib
generate the web site and copy the javadoc into c:\tmp\pmd\docs\javadoc
Zip it up, rename it pmd-bin-1.0rc2.zip

All is well, so time to tag:
cvs ci -m "preps for release"
cd c:\data\pmd
cvs rtag -D tomorrow "pmd_release_1_0rc2" pmd

Prepare source release:
rmdir /q /s c:\tmp\pmd
mkdir c:\tmp\pmd
cvs export -d c:\tmp\pmd -r pmd_release_1_0rc2 pmd
copy pmd\lib\pmd-1.0rc2.jar c:\tmp\pmd\lib
zip it up, rename it to pmd-src-1.0rc2.zip

if you see a bug and fix it, you can delete the release using:
cvs rtag -d pmd_release_1_0rc2 pmd
and then retag everything

FTP the zip file to SF
ftp upload.sourceforge.net
generic userid/password: anonymous/tomcopeland@users.sourceforge.net
cd incoming
bin
put pmd-bin-1.0rc2.zip
put pmd-src-1.0rc2.zip

Go to Admin, Edit/Release Files, click on Add new release
Paste stuff into the changelog/readme boxes
Add the pmd-bin-1.0rc2.zip file
Add the pmd-src-1.0rc2.zip file
Classify the file

Redo the web site

Submit some news saying "hey, new release!"