Changes between Version 3 and Version 4 of CodeManagementReleaseProcess


Ignore:
Timestamp:
11/25/11 16:22:17 (5 years ago)
Author:
jim
Comment:

git updates

Legend:

Unmodified
Added
Removed
Modified

  • CodeManagementReleaseProcess

    v3 v4  
    55= Code Management and Release Process = 
    66 
    7 The code for the website and other projects - like the Sharing Engine(s) - including all Drupal core, contrib and custom files (but excluding settings and uploaded assets) is stored in a set of Git repositories available at https://tech.transitionnetwork.org/trac/browser. 
     7The code for the website and other projects - like the Sharing Engine(s) - including all Drupal core, contrib and custom files (but excluding settings and uploaded assets) is stored in a set of Git repositories on Github at https://github.com/i-jk/Transition-Network 
    88 
    9 The code was previously in a SVN repository, details of which are at CodeManagementReleaseProcessOld. 
     9''The code was previously in a SVN repository, details of which are at CodeManagementReleaseProcessOld.'' 
    1010 
    1111== Principles == 
    … …  
    1313 
    1414 1. You '''never hack Drupal core''' 
    15  1. Developers work on their own machines and check/push code into into the repository ONLY when their code TESTED functional. 
    16  1. The [http://dev.transitionnetwork.org.webarch.net/ development server (DEV)] mirrors the LIVE environment must be used to test this code before moving to LIVE. This server also holds the Git repositories. 
    17  1. There is a [http://test.transitionnetwork.org.webarch.net/ TEST server] which can also be used as required, but is optional unless there is a lot of development work going on or many developers need to test their work in preparation for a release to LIVE. 
    18  1. The LIVE server ONLY EVER gets tagged releases pulled onto it. Such releases must be tested (both on a local developer machine AND on DEV) prior to tagging and release. Hence, the LIVE server moves from one tagged release to the next. 
     15 1. You understand Git -- go to http://gitref.org/ and start reading if not. 
     16 1. Developers work on their own machines and push code into into the 'development' or 'live branches ONLY when their code TESTED functional. 
     17 1. The [http://dev.transitionnetwork.org.webarch.net/ development server (DEV)] mirrors the LIVE environment in setup, and must be used to test this code before moving to LIVE. This server has the 'development' branch on it. 
     18 1. There is a [http://test.transitionnetwork.org.webarch.net/ TEST server] which can also be used as required, but is optional unless there is a lot of development work going on or many developers need to test their work in preparation for a release to LIVE. '''TEST does not presently have Git enabled''' - contact Jim if this is needed. 
     19 1. The LIVE server ONLY EVER gets what is in the 'live' branch pulled onto it. ALL releases must be tested (both on a local developer machine AND on DEV) prior to merging with the 'live' branch and being pushed to the LIVE server. 
    1920 1. Database backups must happen before each release to LIVE - this way each release on LIVE has an associated database backup. Go to 'Site building' -> 'Backup & migrate' (or use the command line NewLiveServer#mysql-backup script) to create the backup. 
    20  1. You can update the test and dev site's databases and files to match the live server using the DevelopmentServer#live2dev script. 
     21 1. You may occasionally want to update the TEST and DEV site's databases and files to match the live server by using the DevelopmentServer#live2dev script. 
     22 
     23---- update to HERE --- 
     24 
    2125 
    2226== Software & Getting Started ==