Changes between Version 1 and Version 2 of CodeManagementReleaseProcessOld

Timestamp:

11/19/10 14:11:47 (6 years ago)

Author:

chris

Comment:

--

CodeManagementReleaseProcessOld

@@ -5 +5 @@
 = Code Management and Release Process =
 
-The code for the site, including all Drupal core, contrib and custom files (but excluding settings and uploaded assets) is stored in an SVN repository available at https://tech.transitionnetwork.org/svn/.
+The code for the site, including all Drupal core, contrib and custom files (but excluding settings and uploaded assets) is stored in an SVN repository available at https://tech.transitionnetwork.org/svn/ and browser:www.
 
 == Overview & Principles ==
@@ -24 +24 @@
  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.
 
+== Comment from Chris ==
+
+Some suggestions:
+
+Developers work on the browser:www/trunk and this is tested on [http://test.transitionnetwork.org/ test.transitionnetwork.org] and [http://dev.transitionnetwork.org/ dev.transitionnetwork.org] as required.
+
+When the code is ready to be deployed to the live server it's tagged, which is an svn copy, eg:
+
+{{{
+  svn cp trunk rel-2010-11-19
+  svn commit -m "Release version 2010-11-19"
+}}}
+
+Then on the live server this is deployed:
+
+{{{
+  sudo -i
+  cd cd /web/transitionnetwork.org/www/
+  svn switch https://tech.transitionnetwork.org/svn/www/rel-2010-11-19/ .
+}}}