Re: Version control

We use CVS and it's really not a pain to deal with. It works well for small
jobs (like just me when I'm doing a small consulting project) or larger
multi-programmer efforts. It is well supported and maintained. And the
price is right.

We keep all of SwiftForth, SwiftX, and several hundred custom projects
(large and small) in a CVS repository. It handles text files (i.e. source
and txt docs) as well as binaries (schematics, spreadsheets, whatever).

If you want a GUI for your client side, check out Tortoise CVS
(www.tortoisecvs.org). Handling checkout of prior releases and concurrent
development on multiple "branches" is trivial.

Leon Wagner
FORTH, Inc.

> -----Original Message-----
> From: sftalk-bounce_at_forth.com [mailto:sftalk-bounce_at_forth.com]On Behalf
> Of alanf2_at_earthlink.net
> Sent: Tuesday, June 01, 2004 12:52
> To: sftalk_at_forth.com
> Subject: [sftalk] Version control
>
>
> Has anyone used "version control" software?
>
> The application I am now working on
> will evolve over time for performance and
> functionality improvement, bug fixes, and
> customization. I will need to keep track of
> version differences in order to diagnose
> bugs and propagate bug fixes and new
> functionality among the various flavors.
> Of crucial importance is responding
> quickly to end-user bug reports on past
> versions, which requires retrieval of past
> version source and preferrably the
> extraction of all changes between it and
> the latest version.
>
> The most commonly seen version control
> packages appear to be either in the
> multi-thousand-$ price bracket, which is too
> expensive, or a pain to deal with, especially
> without Unix or Linux. CVS (Concurrent
> Version System) is the prime example of
> the latter: designed for large multi-site
> team projects, and no small project in itself
> to install and use. In my case, a single-user
> system without fancy file checkout locks and
> client-server repository access will do.
>
> Has anyone found such a thing (at a modest
> price)? Are they in general compatible with
> Forth? It would be nice to be able to use it
> with text documents, schematics, etc; are
> they generalized enough for this?
>
>
> Gratefully,
>
> Alan Furman
>
> ----------------------------------------------------------------------
> sftalk_at_forth.com The SwiftForth programming discussion email list
> To unsubscribe, send subject "unsubscribe" to sftalk-request_at_forth.com
> For list command help, send subject "help" to sftalk-request_at_forth.com
> Message archives are located at http://www.forth.com/archive/sftalk
> ----------------------------------------------------------------------
> This list is a forum for SwiftForth users. For product support and bug
> reports, please send email to support_at_forth.com
> ----------------------------------------------------------------------
>
>

----------------------------------------------------------------------
sftalk_at_forth.com The SwiftForth programming discussion email list
To unsubscribe, send subject "unsubscribe" to sftalk-request_at_forth.com
For list command help, send subject "help" to sftalk-request_at_forth.com
Message archives are located at http://www.forth.com/archive/sftalk
----------------------------------------------------------------------
This list is a forum for SwiftForth users. For product support and bug
reports, please send email to support_at_forth.com
----------------------------------------------------------------------
Received on Tue Jun 01 2004 - 13:11:09 PDT