Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

ajtaylor (1283)

  (email not shown publicly)

Journal of ajtaylor (1283)

Thursday May 29, 2003
11:53 AM

Advanced CVS usage

[ #12504 ]

I've posted a meditation on perlmonks about more fully using all the features CVS has to offer, namely branches (which I've rarely used). I want to "Take it to the next level" so to speak.

The gist of it is that we'll use the trunk for "stable" releases, and create branches for each new project/bugfix. Each branch will eventually be merged back into the trunk, and a new release tagged on the trunk. I would appreciate any tips the community here has to offer, especially in the way of managing a complex CVS tree.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • I think thats backwards. When you checkout something from CVS you always want the 'latest' stuff. (any project both at work and public).

    At work we branch once we start a new release and wrap up the old release, then we merge the bug fixes and such into the trunk on a regularly so you don't have to make the bug fix twice.



  • but I don't think it will work for us. In our case there are 2 developers here, and we generally don't work on the same projects. The release dates for said projects will probably never coincide. So whatever we do will have to support independent projects.

    If all development is on the trunk, then we can only check in changes once we know they are stable & won't break the trunk. This has the benefit of letting each other know quickly if API's change. But it also can potentially hurt the other developer

    "Perl users are the Greatful Dead fans of computer science." --slashdot comment