INFO

• The following is a proposed process that describes how we handle Sakai source code modifications

UCD New Tools

• If a new tool is well isolated so that it can be added in it's own subversion module, than all the initial development will take place in its trunk

  • e.g. ucd-stats, scorm

• If a new tool modifies an existing module, then one should create a JIRA branch for that affected module. The JIRA branch will be a copy of either trunk or a branch.

  • e.g. Some functionality of ServiceXYZ (SAK-1234) needs to modify an existing Sakai component's module

    • Create the new module space: ucd-sakai/ServiceXYZ/trunk, ../branches, ../tags

    • Copy existing components (trunk|branch) and create a JIRA branch

      • svn copy https://mware.ucdavis.edu/svn/ucd-sakai/component/trunk https://mware.ucdavis.edu/svn/ucd-sakai/component/branches/SAK-1234