History of ReleaseProcess

{maketoc}
!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
# 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.
# 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 ~~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

!Test New Release
# 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.
# continue only when no issues were found until the installation has been completed and at least some pages have loaded successfully.

!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 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
TODO

!Testing
__**VERY IMPORTANT**__
# On your local workstation, extract and test a clean install of one of the builds - and problems should be resolved and the ReleaseProcess started again.
# For the builds that you do not test, confirm that they extract correctly OR test the integrity of the archives using the appropriate tools.

!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
** ftp upload.sf.net
** Name (upload.sf.net): anonymous
** Password:
** ftp> cd incoming
** ftp> bin
** ftp> hash
** ftp> prompt
** ftp> mput bitweaver_x.y.z.*
** ftp> bye
# Login as SF admin at [http://sf.net/projects/bitweaver]
# Go to [http://sourceforge.net/project/admin/editpackages.php?group_id=141358|Admin / File Releases]
# At the bottom of the page, click __Edit Releases__ on ''bitweaver'' Package Name
# At the top of the list, should be the previous release. Click the __Edit this release__ link
# Scroll down to __Step 2__
# Select the check boxes for the 3 files you uploaded previously
# Click __Add files and/or Refresh View__
# Scroll down to __Step 3__
# For each of the individual files
** files from the previous release, change the Release drop down box to __bitweaver: Release - past releases__
** change the __Processor__ drop down box to __Platform-Independent__
** change the __File Type__ drop down box to the appropriate extension
** Click on the __Update/Refresh__ button for that file
# Scoll to __Step 1__
# Change the:
** __Date__ - to todays date
** __Release Name__ - to ''Release x.y.z'' eg __Release 1.0.1__
# Click __Submit/Refresh__ at the bottom of the page
# Scroll down to __Email Release Notice__
# Check the __I'm sure__ box
# Click __Send Notice__

!CVS tag
# finally add a __CVS Tag__ by doing: __cvs rtag -r Rx Rxyz bitweaver__ e.g.: cvs rtag -r R1 R103 bitweaver
__
!Announce
# Annouce on
## IRC
## Forums
## Mailing List
## main page ((bitweaver))
# Revisit MediaBlitz to spread the word
# Add upgrade information to bitweaverUpgrade
# Update the bitweaver release module
# Make sure Release_1.0 is up to date
# Edit the file /home/bitweaver/live/bitversion.txt on packard and add appropriate version


!New Releases
!!So how does bitweaver handle development of new releases?
At any time there are 3 active versions of bitweaver refered to as STABLE, TESTING, and DEVELOPMENT. We intend to follow the spirit of the [http://www.debian.org/releases/|debian release process].
!!!STABLE
This is the latest stable release for production use. This is STABLE and we mean __STABLE__, and have very high standards. If you need bitweaver in a production environment, this is for you. Only changes allowed here are to fix major bugs. Bug fixes here are pushed forward to TESTING and DEVELOPMENT.
These will be packaged as <edition>_FR1. If additional fixes are deemed necessary, packages called <edition>_FR2, FR3, ect.
!!!TESTING
This is the code being prepared for the next realease. This code should be considered very useable for a live site. No new features are added, but features are tested and fixed. Bugs are also fixed here, and those changes get pushed forward to DEVELOPMENT.
As realease gets close, we will periodicaly package release canidates called <edition>_RC1, <edition>_RC2 ect...
A release candidate, if good enough, will be transformed to a STABLE version if the TestProcess shows that it is OK. In practice it might happen that one or two critical bugs gets fixed before moving an almost good RC to a stable version if it is reasonable to belive that these corrections has few feature interactions.
!!!DEVELOPMENT
This is the cutting edge and where new features get added.
Periodic tarballs will be made availible.
----
Both TESTING and DEVELOPMENT will produce weekly builds named <edition>_WB_<date>.
Page History
Date/CommentUserIPVersion
25 Jan 2006 (22:32 UTC)
xing194.152.164.4533
Current • Source
xing194.152.164.4532
View • Compare • Difference • Source
xing194.152.164.4531
View • Compare • Difference • Source
xing194.152.164.4530
View • Compare • Difference • Source
xing194.152.164.4529
View • Compare • Difference • Source
xing194.152.164.4528
View • Compare • Difference • Source
xing194.152.164.4527
View • Compare • Difference • Source
xing194.152.164.4526
View • Compare • Difference • Source
xing194.152.164.4525
View • Compare • Difference • Source
xing194.152.164.4524
View • Compare • Difference • Source
Stephan Borg218.214.1.11323
View • Compare • Difference • Source
Stephan Borg218.214.1.11322
View • Compare • Difference • Source
Stephan Borg218.214.1.11321
View • Compare • Difference • Source
Stephan Borg218.214.1.11320
View • Compare • Difference • Source
Stephan Borg218.214.1.11319
View • Compare • Difference • Source
xing194.152.164.4518
View • Compare • Difference • Source
xing194.152.164.4517
View • Compare • Difference • Source
xing194.152.164.4516
View • Compare • Difference • Source
xing194.152.164.4515
View • Compare • Difference • Source
Stephan Borg218.214.1.11314
View • Compare • Difference • Source
Stephan Borg218.214.1.11313
View • Compare • Difference • Source
Stephan Borg218.214.1.11312
View • Compare • Difference • Source
SEWilco209.98.144.1611
View • Compare • Difference • Source