SVN branch, tags and other

Bug #571291 reported by nik on 2010-04-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ace_driver
High
Unassigned

Bug Description

Svn structure!!

nik (nmitsou) on 2010-04-28
Changed in acedriver:
importance: Undecided → High
nik (nmitsou) wrote :

So, I am changing the svn structure like this:

- Trunk
    - ACE
       - Driver
       - Configuration
       - Docs
- Branches
- Tags

On Trunk we will commit the latest version of the code

On Tags, certain versions of the code will be kept (for history / not for active development)
    e.g. ver1.0 (autonomously around the building)
    e.g. ver3.0 (ACE scenario)

On Branches, different paths of development (experimental or for bug fixing)
    e.g. Experiment with next ROS version
          -> Create new branch (copy from trunk)
          -> Update all algorithms, interfaces
          -> Make it stable
          -> If ok, move it to trunk

    e.g. Fix a serious bug
          -> Create new branch (copy from trunk)
          -> Fix the bug slowly
          -> If ok, move it to trunk

More here: http://ariejan.net/2006/11/24/svn-how-to-structure-your-repository/

Any comments?

nik (nmitsou) on 2010-04-29
Changed in acedriver:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers