FRAT/Development: Difference between revisions
From KitwarePublic
< FRAT
Jump to navigationJump to search
No edit summary |
|||
(4 intermediate revisions by the same user not shown) | |||
Line 14: | Line 14: | ||
<br> | <br> | ||
<b>For Users</b> | <b>For Users</b> | ||
* [[FRAT/ | * [[FRAT/Install_Guide | Installation Guide]] | ||
* [[FRAT/Slicer | FRAT with Slicer]] | * [[FRAT/Slicer | FRAT with Slicer]] | ||
<br> | <br> | ||
Line 20: | Line 20: | ||
<br> | <br> | ||
<b>For Developers</b> | <b>For Developers</b> | ||
* Development Docs | * [[FRAT/Library | libFRAT]] | ||
* [[FRAT/Documentation | API Documentation]] | |||
* [[FRAT/Development | Development Docs]] | |||
<br> | <br> | ||
<hr> | <hr> |
Latest revision as of 22:17, 11 August 2011
__NOTITLE__
|
Development GuidelinesCurrent development on FRAT is done using git. The repository is currently hosted at: Development EnvironmentTo gain write access to the repository, contact one of the administrators. Once gained, follow the steps in the Installation Guide except use the read/write address to clone the repository git clone git@gitorious.org:frat/frat.git WorkflowDue to the small developer community, we follow a simple branchy workflow in git. The core workflow is:
git checkout master git checkout -b MY_TOPIC
<edit files> git commit -a <Add descriptive commit message>
git checkout master git merge --no-ff --log MY_TOPIC
git push NOTE: For minor bug fixes, commits directly onto master are ok. In this case, make sure that the commit message reads something like: BUG: brief bug description This is a full description of the bug and what I did to fix it. |