Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Not sure if you've tried this, but some good information can be found by going to Google and entering "software branching patterns". The first link has more patterns than you will ever want to see.

Also, be sure to check out http://www.tldp.org/REF/CVS-BestPractices/html/index.html, though the book you list may have much/all of this.

I can't help with complexity. I'm the only one using my repository so I can get away with developing on the trunk. When I release I tag it and create a branch for bug fixes, which eventually get merged back into the trunk. Any very long term development I move off to it's own special branch (since I don't tend to have much of that). If others start using the repository with me, I'll may have to limit the trunk to stable releases as you have done. Though I imagine merging will be more painful.

Even though I'm the only one using the repository, I've found it is very important to write out the rules (i.e. when to tag and branch, when to merge, what to name tags, when to retire a branch for good, etc.) so I don't start cutting corners, forgetting, and getting into real trouble. I also tend to keep a text listing of all branches, their current state (active/retired) and purpose. This is pretty low tech, but it works for me.


In reply to Re: [OT] Advanced CVS usage by bluto
in thread [OT] Advanced CVS usage by drewbie

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others studying the Monastery: (7)
As of 2024-03-28 19:47 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found