Changes

Release Management

615 bytes removed, 12:13, 16 October 2013
/* Source Code Organization */
= Development =
== Source Code Organization ==
Every We have the stoney cloud related repositories like installer, node-integration, ... These we keep as is (for the moment). The web interface consists a bunch of modules. Each module has a separate GitHub git repository containing the following sub-structure:
GitHub:
See the [[Modularisation]] page for details.
 
<s>
Every such component-directory contains the following sub-structure:
 
* trunk
* tags
* branches
 
For every release of a component a tag is created in <code>/tags</code>
 
Development is primarily done in <code>/trunk</code>. Branches are created either for maintaining a specific minor-version of the package or for developing new features (at developers discretion).
 
For doing a complete stoney cloud release, a new branch/tag is created in the component ''stoney cloud'' which contains git repository references to the corresponding tags/branches of the other components.
 
Advantage:
* clean separation (of release cycles) between components
* easier branching on a per-component basis
 
Disadvantage:
* harder to make a complete release (requires updating the references)
</s>
== Committing ==
SLB, editor, reviewer
3,368
edits