Re: searching for yoda - a developer's tale

From: Frank (abc_at_def.ghi)
Date: 02/24/05 

Date: Thu, 24 Feb 2005 11:08:39 +0100

dexter@uwm.edu wrote:
*snip*
> and handle versioning through cvs
> (https://www.cvshome.org/).

Sounds like you're on the right track, lots of sensible tech listed here.

I'd go with subversion for version control, though. It's a 'better cvs',
superior from a devs point of view, and also a breeze to admin, so less
chance of something going awry.

You may also want to consider some kind of testing framework. JUnit
seems ubiquitous these days.

Relevant Pages

  • Re: Controlling project version
    ... over CVS. ... I've used CVS and Subversion quite a lot for a number of years. ... The branching in Subversion is a gazillion times better than CVS if you ... started playing with Git. ...
    (php.general)
  • Re: Xcode and Subversion
    ... Subversion aims to be a 'better CVS than CVS'. ... All CVS and Subversion clients access a master ... repository: changes are committed to the repository by one client, ...
    (uk.comp.sys.mac)
  • Re: Alternatives to Visual Sourcesafe?
    ... I would say that subversion exists for those that can't set up CVS. ... other major projects using it :-) It's a mature product. ... run a CVS server on a laptop - in fact - it is running right now on the laptop I'm using to type this ...
    (comp.arch.embedded)
  • Re: (OT) Team programming tools
    ... > people, we have 5 programmers, including me. ... Visual Source Safe, CVS, and Subversion to this point. ... Linux is not The Answer. ...
    (Debian-User)
  • Re: IBMs CCCA and customized LCPs for Enterprise COBOL migration
    ... managing concurrent or parallel development. ... CVS and Subversion are excellent for concurrent development. ... very common for production and QA fixes to be overwritten by the next release. ...
    (comp.lang.cobol)
Loading