Hi,

normally, people develop in trunk and whenever the code is ready, a
release is done.

Normally, related packages are packed together into stacks. When a
release is done, the stack's version number is increased and the
current dev-branch (trunk in most cases) is tagged. For instance, when
the new version 1.3 of stack foo is released, the tag tags/foo-1.3 is
created. In addition, a branchs named according to the ros distro
names the release is done against is created,
e.g. branches/diamondback.

For more information on releasing, have a look at

http://www.ros.org/wiki/release

Lorenz

> Hi all:
> 
> At our centre, we are working to bring our ROS repository public. I want
> to ask the people which currently maintain a ROS repository what is the
> kind of workflow used with SVN.
> 
> Our objective is to keep trunk stable enough, so intrusive changes, work
> in progress or new packages preferably should not appear there.
> 
> Using a branch comes to mind as the natural way, but "branching" the
> whole repo for every project (new packages or new features) could not be
> the best idea.
> 
> For repo maintainers: what is your current workflow? commits in trunk
> directly? branching the whole repo? partial branching? two repositories? =)
> 
> Thanks a lot.
> 



> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users


-- 
Lorenz Mösenlechner            | moesenle@in.tum.de
Technische Universität München | Karlstraße 45
80335 München                  | Germany
http://ias.cs.tum.edu/         | Tel: +49 (89) 289-26910