Switch the 'modify' code of admin/field.php to use templates
[bugdar.git] / docs / release_procedure.txt
1 These are the instructions to follow before a release is finalized.
2
3 SVN $Id$
4
5 ###################################################################
6
7 1) Use docs/datatools.php to export the default data store file (in docs/)
8
9 2) Use docs/datatools.php to generate the contents of install/default_data.php
10
11 3) Use docs/datatools.php to dump the current settings into install/settings.php
12
13 4) Run a "svn diff" between the templates on trunk and the most recent release,
14 storing the diff in install/templates/<OLD RELEASE - NEW RELEASE.diff>
15
16 5) Update the po/en_US.pot file using ISSO's makepo.sh.php tool
17
18 6) Move all the changes from docs/schema_changes.sql to an upgrade script
19
20 7) Update the schema file using tools/schema.php
21
22 8) Test the installer to make sure it still works, and then test the upgrade script
23
24 9) Update the Blue Static tracker to ensure that the upgrade script works in a
25 production environment
26
27 10) Copy the contents of docs/changelog.txt to the bluwww site
28
29 11) Update all the links on bluwww to point to the most recent download
30
31 12) Update the bluwww playground/PRODUCTS.php record for this version
32
33 13) Tag the version in SVN. Be sure to change the svn:externals to specify a
34 revision for ISSO!
35
36 14) Export the tagged version to the Blue Static playground
37
38 15) Update the Blue Static site from the latest bluwww
39
40 16) Test the download links to ensure the sources are okay
41
42 17) Tag the bluwww update in the repository