History of ReleaseProcess
Version 32 | Current version | |
---|---|---|
Change version in code
Archive Generationarchive 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
Release Test
Create zip file
Create bz2 file
Create rpm fileTODOArchive Testing
Cleanup
Upload files to SourceForge
Final tests
CVS tag
Announce
New ReleasesSo 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 debian release process.STABLEThis 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. TESTINGThis 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. DEVELOPMENTThis 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>.</date></edition></edition></edition></edition></edition> | Change version in code
Archive Generationarchive 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
Release Test
Create zip file
Create bz2 file
Create rpm fileTODOArchive Testing
Cleanup
Upload files to SourceForge
Final tests
CVS tag
Announce
New ReleasesSo 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 debian release process.STABLEThis 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. TESTINGThis 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. DEVELOPMENTThis 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>.</date></edition></edition></edition></edition></edition> |