pmd/pmd-jedit/etc/doing_the_next_pmd_jedit_release.txt

update the release date in the changelog
change config/pmd.props to reflect actual pmd.jar file version
change config/pmd.props to reflect pmd-jedit release 1.1
change config/jedit.html to reflect pmd-jedit release 1.1
change the build.xml to reflect pmd-jedit release 1.1

Create the binary release:
ant release
move the zip file into c:\tmp
TESTS:
1) Can you run jedit ok?
2) Can you run it it on a file and find some unused code?
3) Are options persistant?

Create the src release:
cvs -q rtag -D tomorrow "pmd_jedit_release_1_1" pmd-jedit
rmdir /q /s c:\tmp\pmd-jedit
mkdir c:\tmp\pmd-jedit
cvs -q export -d c:\tmp\pmd-jedit -r pmd_jedit_release_1_1 pmd-jedit
copy pmd-jedit\lib\PMDJEditPlugin-1.1.jar c:\tmp\pmd-jedit\lib
zip it up, rename it to pmd-jedit-src-1.1.zip

FTP the zip file to SF
ftp upload.sourceforge.net
generic userid/password: anonymous/tom@infoether.com
cd incoming
bin
put pmd-jedit-src-1.1.zip
put pmd-jedit-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-jedit-src-1.1.zip file
Add the pmd-jedit-bin-1.1.zip file
Classify the file

Submit some news saying "hey, new release of the JEdit plugin!"

change config/pmd.props to reflect the next plugin version
change jedit.html to reflect the next plugin version
change build.xml to reflect the next plugin version