next up previous
Next: Example Up: Subversion in DataCore-style Previous: Subversion in DataCore-style

Structure

DataCore splits the programming into 4 pieces:
  1. trunk
    In the trunk only the chief programmer has a say. He controls it, and only he can code into it. Out of the trunk there will be created the releases, if the programm is in such an advanced state.
  2. branches
    Here all the Developpers create their stuff. Usually, everyone gets his own branch, either one that is named after his name, or one that is named by the Part he is creating
    As an example, when I am joining a project, and i just want to try some things with the code, I call my branch: branches/myname. Over time I advance and understand the code, and I am ready to do my part. I decided to do the part of the programm, that manages the display, so I name the branche: branches/display.
    I think you get the point.
  3. tags This is nothing else, than a copy of the trunk. The only difference here, is that this wont evolve over time. You can say, that a tag is a copy of the trunk at a certain revision.
    They are usually called tags/[versionnumber]
  4. releases
    This is the same thing as a tag, with the slight difference, that it is a real release. With this you are going public. Usually you don't do this with a tag.


next up previous
Next: Example Up: Subversion in DataCore-style Previous: Subversion in DataCore-style
Benjamin Grauer 2004-06-04