diff --git a/pmd-jbuilder/etc/doing_the_next_pmd_jbuilder_release.txt b/pmd-jbuilder/etc/doing_the_next_pmd_jbuilder_release.txt
index 9040919941..387c1ffe36 100644
--- a/pmd-jbuilder/etc/doing_the_next_pmd_jbuilder_release.txt
+++ b/pmd-jbuilder/etc/doing_the_next_pmd_jbuilder_release.txt
@@ -6,16 +6,16 @@ move the zip file into c:\tmp
 
 Create the src release:
 cd lib
-cvs add -kb PMDOpenTools-0.3.jar
-cvs rm PMDOpenTools-0.2.jar
+cvs add -kb PMDOpenTools-0.4.jar
+cvs rm PMDOpenTools-0.3.jar
 cvs ci -m "adding new jar, removing old one"
 cd c:\data\pmd
 rmdir /q /s pmd-jbuilder\build
-cvs rtag -D tomorrow "pmd_jbuilder_release_0_3" pmd-jbuilder
+cvs rtag -D tomorrow "pmd_jbuilder_release_0_4" pmd-jbuilder
 rmdir /q /s c:\tmp\pmd-jbuilder
 mkdir c:\tmp\pmd-jbuilder
-cvs export -d c:\tmp\pmd-jbuilder -r pmd_jbuilder_release_0_3 pmd-jbuilder
-zip it up, rename it to pmd-jbuilder-src-0.3.zip
+cvs export -d c:\tmp\pmd-jbuilder -r pmd_jbuilder_release_0_4 pmd-jbuilder
+zip it up, rename it to pmd-jbuilder-src-0.4.zip
 
 unzip binary release into the JBuilder lib/ext directory
 TESTS:
@@ -23,7 +23,7 @@ TESTS:
 2) Can you run it it on a file and find some unused code?
 
 if you see a bug and fix it, you can delete the release using:
-cvs rtag -d pmd_jbuilder_release_0_3 pmd
+cvs rtag -d pmd_jbuilder_release_0_4 pmd
 and then retag everything
 
 FTP the zip file to SF
@@ -31,8 +31,8 @@ ftp upload.sourceforge.net
 generic userid/password: anonymous/dcraine@infoether.com
 cd incoming
 bin
-put pmd-jbuilder-src-0.3.zip
-put pmd-jbuilder-bin-0.3.zip
+put pmd-jbuilder-src-0.4.zip
+put pmd-jbuilder-bin-0.4.zip
 
 Go to Admin, Edit/Release Files, click on Add new release
 Paste stuff into the changelog/readme boxes