From 43debfb70b389c62476cae0744d90e9794772ace Mon Sep 17 00:00:00 2001 From: Robert Sesek Date: Fri, 16 Feb 2007 07:15:11 +0000 Subject: [PATCH] r1414: Adding an instructions file on how to prepare for releases --- docs/release_procedure.txt | 39 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 docs/release_procedure.txt diff --git a/docs/release_procedure.txt b/docs/release_procedure.txt new file mode 100644 index 0000000..71e0d1a --- /dev/null +++ b/docs/release_procedure.txt @@ -0,0 +1,39 @@ +These are the instructions to follow before a release is finalized. + +SVN $Id$ + +################################################################### + +1) Use docs/datatools.php to export the default data store file (in docs/) + +2) Use docs/datatools.php to generate the contents of install/default_data.php + +3) Use docs/datatools.php to dump the current settings into install/settings.php + +4) Run a "svn diff" between the templates on trunk and the most recent release, + storing the diff in install/templates/ + +5) Update the po/en_US.pot file using ISSO's makepo.sh.php tool + +6) Move all the changes from docs/schema_changes.sql to an upgrade script + +7) Test the installer to make sure it still works, and then test the upgrade script + +8) Update the Blue Static tracker to ensure that the upgrade script works in a + production environment + +9) Copy the contents of docs/changelog.txt to the bluwww site + +10) Update all the links on bluwww to point to the most recent download + +11) Update the bluwww playground/PRODUCTS.php record for this version + +12) Tag the version in SVN + +13) Export the tagged version to the Blue Static playground + +14) Update the Blue Static site from the latest bluwww + +15) Test the download links to ensure the sources are okay + +16) Tag the bluwww update in the repository \ No newline at end of file -- 2.22.5