pmd/pmd-jdeveloper/etc/doing_the_next_pmd_jdeveloper_release.txt

33 lines
1.1 KiB
Plaintext
Raw Normal View History

update the release date in the changelog
change the build.xml to reflect pmd-jdeveloper release 0.2
Create the binary release:
ant release
TESTS:
1) Does it unzip neatly on top of the jdev/ext/lib directory?
2) Can you run it it on a file and find some unused code?
3) Are options persistant?
Create the src release:
cd ~/data/pmd/
cvs -q rtag -D tomorrow "pmd_jdeveloper_release_0_2" pmd-jdeveloper
rm -rf ~/tmp/pmd-jdeveloper
mkdir -p ~/tmp/pmd-jdeveloper
cvs -q export -d tmp -r pmd_jdeveloper_release_0_2 pmd-jdeveloper
mv tmp/* ~/tmp/pmd-jdeveloper
rmdir tmp/
cp pmd-jdeveloper/lib/pmd-jdeveloper-0.2.jar ~/tmp/pmd-jdeveloper/lib
cd ~/tmp
zip -q -r pmd-jdeveloper-src-0.2.zip pmd-jdeveloper
ncftpput upload.sourceforge.net incoming/ pmd-jdeveloper-bin-0.2.zip
ncftpput upload.sourceforge.net incoming/ pmd-jdeveloper-src-0.2.zip
Go to Admin, Edit/Release Files, click on Add new release
Paste stuff into the changelog/readme boxes
Add the pmd-jdeveloper-src-0.2.zip file
Add the pmd-jdeveloper-bin-0.2.zip file
Classify the file
Submit some news saying "hey, new release of the jdeveloper plugin!"