Changes between Version 35 and Version 36 of DevelopmentProcedure

Timestamp:

03/31/14 15:43:04 (11 years ago)

Author:

ehansen

Comment:

—

DevelopmentProcedure

@@ -6 +6 @@
 1. Before starting a new development task, you should first make sure you have an up to date version of the code.  Please see [GitoliteProcess this page] for information about using gitolite.
 {{{
-  git clone ssh://orda@botwin.pas.rochester.edu
+  git clone ssh://orda@botwin.pas.rochester.edu/astrobear
 }}}
-1. Also make sure there is a ticket outlining what development you plan on doing.  Create one if necessary!
+1. Move to your new repo, and check out the development branch
+{{{
+  git checkout development
+}}}
+1. Make sure there is a ticket outlining what development you plan on doing.  Create one if necessary!
 1. Then create a new branch off of the development branch using the ticket id as the branch name
 {{{
@@ -29 +33 @@
   git push
 }}}
-1.  You can repeat steps 5-7 as many times as you want until the feature is complete.  Then please notify [mailto:astrobear_dev@pas.rochester.edu] and we will merge your changes into the development branch and the next release.
+1.  You can repeat steps 6-8 as many times as you want until the feature is complete.  Then please notify [mailto:astrobear_dev@pas.rochester.edu] and we will merge your changes into the development branch and the next release.