I did not say I did not use version control. By VCS I refer to
the programs such as fossil, git, mercurial... used for doing
such. I am using Fossil for my current project in parallel with
my own way of handling versions. Embarcadero RAD Studio
incorporates Git, Mercurial, and Subversion into the IDE. Had
issues with them, so I tried fossil. Still evaluating its utility.
What I meant was I end up spending much time trying to get the
tools to do what I want it to do versus how it wants to do it.
Especially when new to the system, a GUI interface is much
better than having to work with yet another list of command line
formats.
I fully see the utility of a VCS on collaborative projects. My
project is for my own research work and is not used by any
clients. I am also the only one who plays with my code. So some
of the utility needed for collaborative efforts becomes
cumbersome for a solo project.
I have a directory tree on various backup drives of my old
versions, one-off programs, and a huge library of my own
utilities. The development system I use (Embarcadero RAD Studio)
has a built-in program manager which juggles the various files
required for the build.
Before I start writing a new function, process, or other
modification, I create a sub-folder of my backup folder which
are numbered in sequence. The file system applies a date to the
creation time of the folder which identifies when the backup was
made. I then simply copy my entire project folder into the
backup folder. If I break the code, or decide to revert the
changes, I restore the project from the desired backup folder.
This is a bit cumbersome way of handling versions, especially
given my main program consists of more than 250 files. Such is
why I am trying out various VCS systems. I am finding them just
as cumbersome of a process with an added layer of things to go
wrong.
------------
Scott Doctor
[email protected]
------------------
On 10/30/2015 12:59 PM, Richard Hipp wrote:
On 10/30/15, Scott Doctor <[email protected]> wrote:
That is my experience with all VCS systems. Even with fossil, I
am having trouble justifying why the hassle is worth the effort.
What do you do when a customer calls to ask about code you sent them
18 months ago? How do you figure out what version of the code they
are running?
When you find an obscure bug that you know was not in the release from
December 2012 but might have been introduced anytime between then and
now, how do you figure out when it was introduced?
How do you add experimental features and make experimental changes?
Do you just start hacking away and hope the changes don't break
anything?
How do you identify versions of your code to your customer?
How do you verify that no stray changes have been introduced into your code?
How do you backup your code?
When you have multiple people collaborating on the same project, how
do you coordinate their changes and ensure that features added by one
developer don't get overwritten and erased by another developers. How
do you know who is working on what? Can you even identify what you
code is?
Seriously. I don't understand how it is possible to make reliable
software without good version control. Is the foundation of
everything.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
