Changes between Version 5 and Version 6 of TrackingSourceCode

Show
Ignore:
Author:
ppreddy@uab.edu (IP: 138.26.125.8)
Timestamp:
04/01/09 13:48:54 (8 months ago)
Comment:

add wiki links StructRepo and SvnCommitNotify

Legend:

Unmodified
Added
Removed
Modified

  • TrackingSourceCode

    v5 v6  
    1 UABgrid development uses Subversion for source code management.  The repository for the the main components of UABgrid are available off this wiki. While this helps us manage our development process, we don't have much control over tools other projects use.  To provide sanity, we are following the process of [http://svnbook.red-bean.com/en/1.5/svn.advanced.vendorbr.html maintaining vendor drops] from the source vendors that we will work with in-house.  If you aren't comfortable working with vendor drops, you can [SourceCodeSandbox set up a sandbox] for exercising your skills.[[BR]] 
     1UABgrid development uses Subversion for source code management.  The repository for the main components of UABgrid are available off this wiki. While this helps us manage our development process, we don't have much control over tools other projects use.  To provide sanity, we are following the process of [http://svnbook.red-bean.com/en/1.5/svn.advanced.vendorbr.html maintaining vendor drops] from the source vendors that we will work with in-house.  If you aren't comfortable working with vendor drops, you can [SourceCodeSandbox set up a sandbox] for exercising your skills. [[BR]] 
    22 
    3 === Structing the Repo === 
     3Related to our organizational effort: 
    44 
    5 An initial SVN layout for organizing the development activity of @lab[[BR]] 
     5 * on the works is an [wiki:StructRepo initial SVN layout] for organizing the development activity in @lab. This structure is not cast in cement, but to provide us a starting point. 
    66 
    7  * Most of the development activity in @lab originates from source product modification and maintenance. Accordingly, the root repository will consist of subdirectories - vendor, trunk, branches and tags 
    8  
    9 [[Image(source:trunk/docs/images/howto-use-repository/repo-root-layout.png)]] 
    10  
    11  * Vendor drop offs will be the starting point of our code maintenance. 
    12  * Trunk will hold the different areas of activity in separate projects. For now, these projects have been identified as: 
    13  
    14 [[Image(source:trunk/docs/images/howto-use-repository/repo-trunk-layout.png)]] 
    15  
    16  * Development scenarios for maintaining scripts/tools 
    17  
    18 [[Image(source:trunk/docs/images/howto-use-repository/tools-workscenarios.png)]] 
    19  
    20  * Demo of the usability of the code, tools maintained in the repository[[BR]] 
    21   A VM instance which acts as a grid node, for eg., sg-submit can be built as follows: 
    22  
    23 [[Image(source:trunk/docs/images/howto-use-repository/howto-build-vm-instance.png)]] 
    24  
    25    
    26  
    27  
    28  
    29  
     7 * how to [wiki:SvnCommitNotify configure SVN to send emails after commits] 
    308 
    319== References ==