# Confirm the release version is correct in __kernel/setup_inc.php__. Commit any changes to CVS as necessary.
!Archive Generation
+^ archive generation has been summarised in the file ~/bin/release_process.sh
+to use it, execute the file and use the new version number as argument:
+e.g.: __. ~/bin/release_process.sh x.y.z__ ^
we need to generate a number of different archives for different users and requirements.
!!Create tar.gz file
# SSH onto packard.bitweaver.org
# __sudo su - bitweaver__
-# From the Bitweaver home directory and execute the __~/live/install/bitweaver_build.sh bitweaver Rx__ script, where __Rx__ is the release you're building for. This checkouts the latest CVS of BW, cleans it up, and prepares it for distribution.
+# From the Bitweaver home directory and execute the __~/live/install/bitweaver_build.sh bitweaver Rx__ script, where __Rx__ is the release you're building for. This checkouts the latest CVS of BW, cleans it up, and prepares it for distribution. (should be possible to us the command: __freshbuild__)
# The script creates a weekly build tar file in the Bitweaver home directory. Rename the ++yellow:bitweaver_bitweaver_wb_yyyyweekww.tar.gz++ file to the appropriate name ie ~~red:++yellow:bitweaver_x.y.z.tar.gz++~~ where __x__ is the major revision, __y__ is the minor revision and __z__ is the release eg bitweaver_1.0.1.tar.gz
+## If you are too lazy to do the MediaBlitz thing, at least update the [http://en.wikipedia.org/wiki/Comparison_of_content_management_systems|wikipedia page]
# Add upgrade information to bitweaverUpgrade
# Update the bitweaver release module
# Update ReleaseSchedule
-# Make sure Release_1.0 is up to date
-# Edit the file /home/bitweaver/live/bitversion.txt on packard and add appropriate version
+# Edit the file __/home/bitweaver/live/bitversion.txt__ on packard and add appropriate version
+# udpate version number in kernel/setup_inc.php to next release number + add beta as release level