In response to your question about the best development environment , many of the replies to this thread recommend CVS. This is a good thing, CVS is a very good version control system.

But you should be aware that this is only part of the pie: version control is not the same thing as a development environment (read: configuration management).

From the 'version management with CVS':

CVSNT can do a lot of things for you, but it does not try to be everything for everyone.

CVS is not:

  • a build system.
  • a substitute for management.
  • a change control or bug tracking system
  • an automated testing suite
  • a process model

    I just want to make the point that version control is only part of configuration management. Adopting a could versioning system will help you a lot, I agree, but there are still some crucial issues to address.

    How will you handle bug reports/fixes/prioritisation? Deployment? Release management? Communication? Spec and code reviews? These issues are as relevant here as how you version your code.

    Finally, if you are looking at CVS, I recommend also taking a long look at Subversion . It aims to address many features absent from CVS (dir, meta-data, atomic operations), but retaining the CVS model and interface.

    In reply to Re: Team Development by bm
    in thread Team Development by WrongWay

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.