update run.bat to point to pmd-0.7.jar
update the release date in the changelog
move rules from "new_for_v_0_7.xml" into a real ruleset file
cvs rm new_for_0_6.xml
cvs add new_for_0_7.xml
update jar task to reflect pmd-0.7
update xdocs/running.xml to reflect pmd-0.7
update docs to mention GUI if it's in a presentable state
update release number in project.xml

set ANT_HOME=c:\ant
ant dist
ant test
Do all the tests run?  OK, then:
ant dist
cvs add -kb pmd-0.7.jar
cvs rm pmd-0.6.jar
cvs ci -m "adding new jar, removing old one"
cd c:\data\pmd
cvs rtag -D tomorrow "pmd_release_0_7" pmd
rmdir /q /s c:\tmp\pmd
mkdir c:\tmp\pmd
cvs export -d c:\tmp\pmd -r pmd_release_0_7 pmd
zip it up, rename it to pmd-0.7.zip
unzip it into c:\tmp\pmd-0.7
clear classpath
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

if you see a bug and fix it, you can delete the release using:
cvs rtag -d pmd_release_0_7 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-0.7.zip

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

SSH in to shell.sourceforge.net
cd /home/groups/p/pm/pmd/build/
./quickgo.sh

Submit some news saying "hey, new release!"