Changes between Version 3 and Version 4 of CodeManagementReleaseProcessOld

Timestamp:

11/22/10 14:58:04 (6 years ago)

Author:

jim

Comment:

almost there!

CodeManagementReleaseProcessOld

@@ -37 +37 @@
 As you modify the source code and theme files on your checked out working copy, the differences between your copy and the Trunk will grow. It's wise therefore to do smaller chunks of work and commit once these specific bits are completed. Clearly, if several developers are working on the same areas at once, you will have to coordinate your work and be more careful.
 
-To update the Trunk with the tested changes you've done so far:
+To update the Trunk (DEV) with the tested changes you've done so far:
 {{{
 cd /the/directory/you're/working/in
+svn commit -m "A sensible description of what you've done"
+}}}
+Make sure you add a good description in case someone needs to roll back a commit to fix an issue. Then, repeat this step until you're ready to...
+
+=== 2. Test on the DEV server ===
+This step is critical because the DEV server mirrors the setup on LIVE. Hence any issues or differences you didn't spot whilst working on your local machine can be ironed out here. It also allows you to get feedback on your work so far as required.
+
+'''Note:''' To get files onto the server, you must have logged into the development server via SSH - for more on how to do this see wiki:DevelopmentServer#SSHaccess.
+{{{
+ssh dev.transitionnetwork.org.webarch.net
+cd web/dev.transitionnetwork.org.webarch.net/www
 svn up
 }}}
-Repeat this step until you're ready to test it all.
+The last command brings the DEV site up to the latest Trunk version. Go to http://dev.transitionnetwork.org.webarch.net/ and enjoy the fruits of your labour.
 
-=== 2. Test on the DEV server ===
+Depending on the changes, you should test properly and then solicit feedback and testing from managers/stakeholders. This is probably on DEV, but could be on TEST if needed.
 
- 1. OPTIONAL: Developer updates the TEST server using same code.
- 1. OPTIONAL: Developer solicits feedback and testing from managers/stakeholders if complex changes or new development. This is probably on DEV, but could be on TEST.
- 1. Once happy, developer tags the code as appropriate (e.g. v1.3.1 "The crown jewels" etc) as a new copy in the LIVE branch. The source of this should be the DEV branch, since TEST server should only test tagged and ready releases before they make it to LIVE.
+=== 3. 'Tag' (copy) the release ===
+Once everyone is happy with the DEV site updates, you will need to 'tags' (svn copy) the release so it's ready to be moved onto the LIVE server - or the TEST site if needed, more on that in a moment.
+
+
+ code as appropriate (e.g. v1.3.1 "The crown jewels" etc) as a new copy in the LIVE branch. The source of this should be the DEV branch, since TEST server should only test tagged and ready releases before they make it to LIVE.
+
+'''OPTIONAL: Test on TEST too''': Use the above command, but replace 'dev' with 'test' and go to http://test.transitionnetwork.org.webarch.net/ to see things are ok.
+
+Test away and, if necessary (because several developers are working on the site, or you are preparing a large release) repeat the process on the TEST server...
+
+
+
  1. OPTIONAL: points 1-5 happen as many times as required to get the release ready, tested and signed off.
  1. Developer backs up and updates LIVE using the latest tagged release. NOT USING MERGE!!! Using 'svn switch' in our case. If there is a problem the developer can always switch back to the previous tagged release for LIVE and examine the issue in TEST.