!Change version in code
|
# Confirm the release version is correct in __kernel/setup_inc.php__. Commit any changes to CVS as necessary.
|
|
-!Create tar.gz file
|
+!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/bitweaver/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.
|
-# The script creates a weekly build tar file in the Bitweaver home directory. Rename the __bitweaver_bitweaver_wb_yyyyweekww.tar.gz__ file to the appropriate name ie __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
|
+# 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 |
# Copy the renamed file to __~/builds__ directory
|
-# Annouce on IRC and mailing list, it is avaiable for testing
|
|
-!Create zip file
|
+!!!~~red:Release Test~~ |
+# download the new file by visiting [http://www.bitweaver.org/builds]. |
+# extract and install the new version of bitweaver solely following the onscreen instructions and watching for any issues. |
+# if issues were found, fix these and restart the ReleaseProcess |
+ |
+!!Create zip file |
# __mkdir ~/test__ in Bitweaver home directory
|
# __tar xvzf bitweaver_x.y.z.tar.gz -C ~/test__ to extract a copy to ''test'' directory
|
# __cd ~/test__
|
# Create a new zip file, using __zip bitweaver_x.y.z.zip -r bitweaver__
|
# Move the file to __~/builds__ directory __mv bitweaver_x.y.z.zip ~/builds/__
|
-!Create bz2 file
|
+ |
+!!Create bz2 file |
# Create a new bz2 file, using __tar cvjf bitweaver_x.y.z.tar.bz2 bitweaver/__
|
# Move the file to __~/builds__ directory __mv bitweaver_x.y.z.tar.bz2 ~/builds/__
|
|
-!Create rpm file
|
+!!Create rpm file |
TODO
|
+ |
+!!~~red:Archive Testing~~ |
+# execute the [#ReleaseTest|testing] procedure for all the different archives if possible. |
|
!Cleanup
|
# Return to the Bitweaver home directory __cd__
|
# Remove test directory __rm ~/test -rf__
|
+ |
!Upload files to SourceForge
|
# __cd ~/builds__
|
# Using anonymous ftp - upload the previous *.gz, *.zip and *.bz2 files to ftp://upload.sf.net/incoming
|