Dale I am pretty confident that mr torvalds world reccomend git for
version control. He did afterall create it. It's distributed and it's
used to manage the Linux kernal with thousands of contributors. All
the coolness I won't expound upon via my phone keyboard.
Progit.org is a good ref
Search "Linus torvalds google" on YouTube for a great talk he gave to
google staff and the source of that quote.
Sent from my iPhone
On Oct 25, 2009, at 9:47 AM, "Dale Bronk" <[email protected]> wrote:
Hmmmmm. So SVN with daily backups (one place I was at did svn
backups every 6 hours) is pointless? So if there was a system
meltdown, we were less than an hour away from being back up with
minimal possible loss. Actually there would most likely be no loss
since every developer has full code sets.
So what does Mr. Torvalds recommend for version control? I recall a
system that uses all developer machines as possible servers. One is
designated the main server (usually a server box and not a developer
box). If that one goes down it automatically switches to another
users box as the main holding place. I don’t remember the name, but
I do remember it being VERY riddled with issues and even with that
software they recommended the main holding place being a server.
So what is wrong with SVN with backups at a minimum of daily?
Dale
From: [email protected] [mailto:[email protected]] On Behalf Of James
Schneider
Sent: Sunday, October 25, 2009 7:58 AM
To: [email protected]
Subject: Re: [AFFUG Discuss] team coding
To paraphrase Linus Torvalds ( credited with creating the Linux
kernel and git version control) "subversion is probably the most
pointless project ever"
My take: a central server holding you code base is a central point
of failure. If you have a subversion server now, maintain it. But if
you dont have something setup you would be insane to choose
subversion over git.
Jed
Sent from my iPhone
On Oct 24, 2009, at 10:30 PM, Ajas Mohammed <[email protected]>
wrote:
Thanks for the clarification Charlie. It makes sense now. I was
about to hit send on my do not agree email. ;-) Without Version
Control, the development process is dangerous. You can do it but
with constant threat of big issues or huge manual process.
SVN is the way to go if you want to do *ANY* kind of development or
coding.
Thanks Cameron for your post. It was very helpful.
<Ajas Mohammed />
http://ajashadi.blogspot.com
We cannot become what we need to be, remaining what we are.
No matter what, find a way. Because thats what winners do.
You can't improve what you don't measure.
Quality is never an accident; it is always the result of high
intention, sincere effort, intelligent direction and skillful
execution; it represents the wise choice of many alternatives.
On Sat, Oct 24, 2009 at 10:26 PM, Cameron Childress <[email protected]
> wrote:
On Sat, Oct 24, 2009 at 9:31 PM, Eric Minor <[email protected]>
wrote:
> I totally disagree. With a version control system like SVN, the
problems
> you mentioned above would be resolve. I work in a shared
development
> environment with a total of 13 programmers. We all work in
parallel on one
> project. Svn manages any conflicts and keep our code in sync. For
large
> projects, I highly recommend SVN coupled with good project
management skills
> for more efficient software development.
It's rare that the same solution fits all cases, so there is certainly
room for interpretation. However, working on ColdFusion code on one
central server does present alot of challenges when different members
of the team are editing files such as Application.cfc or other core
includes. This can be managed in some cases, but there are plenty of
situations where someone edits a file central to the entire app which
puts everyone's work at a halt for a period of time.
Working on a central server and giving each developer their own folder
and/or port, or setting up CF as multi-instance are good ways to keep
developers from stepping on each other's toes too.
For my teams, more recently we're just about always setup to do
development on each local workstation. Local workstation development
is particularly valuable when team members may be working remotely
some or all of the time, or intermittently connected.
Doing development from an airplane is difficult when using a shared
server, for example.
In the end though, there is no "one uber solution" - it's what works
best for your team.
YMMV.
-Cameron
-------------------------------------------------------------
To unsubscribe from this list, simply email the list with
unsubscribe in the subject line
For more info, see http://www.affug.com
Archive @ http://www.mail-archive.com/discussion%40affug.com/
List hosted by http://www.fusionlink.com
-------------------------------------------------------------
-------------------------------------------------------------
To unsubscribe from this list, simply email the list with
unsubscribe in the subject line
For more info, see http://www.affug.com
Archive @ http://www.mail-archive.com/discussion%40affug.com/
List hosted by FusionLink
-------------------------------------------------------------
