update run.*, astviewer.*, cpd.jnlp, cpdgui.bat, build.xml to point to pmd-1.1.jar
update xdocs/running.xml, integrations.xml, installing.xml to reflect pmd-1.1
update the release date in the changelog
move rules from "newrules.xml" into a real ruleset file
update release number in project.xml

ant dist test
Do all the JUnit tests run?  OK, then:
ant dist

TESTS: Can you
1) run 1 file and get a report
./run.sh ~/tmp/Test.java xml rulesets/unusedcode.xml
./run.sh ~/tmp/Test.java html rulesets/unusedcode.xml
2) run the Ant 'pmd' task and get a report
ant pmd

cd ..
./docs all

Prepare binary release:
rm -rf ~/tmp/pmd-1.1
mkdir -p ~/tmp/pmd-1.1/etc
mkdir ~/tmp/pmd-1.1/lib
cp ../LICENSE.txt run.* cygwin-run.sh build.xml cpdgui.bat changelog.txt astviewer.* ~/tmp/pmd-1.1/etc
cp ../lib/pmd-1.1.jar ../lib/xmlParserAPIs-2.0.2.jar ../lib/xercesImpl-2.0.2.jar ../lib/jaxen-core-1.0-fcs.jar ../lib/saxpath-1.0-fcs.jar  ~/tmp/pmd-1.1/lib/
cp -R xslt/ ~/tmp/pmd-1.1/etc/xslt/
cp -R ../target/docs ~/tmp/pmd-1.1
cd ~/tmp
zip -q -r pmd-bin-1.1.zip pmd-1.1/
cd -

Time to tag:

cd ../../
cvs -q rtag -D tomorrow "pmd_release_1_1" pmd

Prepare source release:
rm -rf ~/tmp/pmd-1.1
mkdir tmp
cvs -q export -d tmp/ -r pmd_release_1_1 pmd
cd pmd/etc
ant jarsrc
cd ../../
cp pmd/lib/pmd-src-1.1.jar tmp/lib/
mv tmp ~/tmp/pmd-1.1
cp pmd/lib/pmd-1.1.jar ~/tmp/pmd-1.1/lib
cp -R pmd/target/docs ~/tmp/pmd-1.1/
cd ~/tmp/
zip -q -r pmd-src-1.1.zip pmd-1.1/

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

ncftpput upload.sourceforge.net incoming/ pmd-src-1.1.zip pmd-bin-1.1.zip

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

Redo the web site

Submit some news saying "hey, new release!"