Took me to literal..
too literally
~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to
date
Get the Free Trial
http://ad.doubleclick.net/clk;203748912;27390454;j
Archive:
Andrew,
A statement like this means you are not very good at your job.
Brian's quite good at his job. I work with him.
its a manual process to update and merge
changes.
Manual within the development branch - there shouldn't be any
outstanding conflicts in anything tagged for QA, staging,
You'd rather introduce a manual process that can't be
auditing, doesn't produce verifiable results, and can
be re-run?
Perhaps he's a contractor.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
Fig Leaf Software provides the highest caliber vendor-authorized
instruction at our
On Sat, Aug 16, 2008 at 8:18 AM, Dominic Watson
[EMAIL PROTECTED] wrote:
There is no way to automatically migrate a file, with 20 changes and only
2
of them are to go to production. This has to be done manually.
You're right, if you have 20 changes to a file and you only want to
push 2
: RE: SVN in Production
/*
/*SVN SHOULD NEVER BE USED IN PRODUCTION...
/*
/*SVN is used to have a revision control system, so that you could roll back
/*to a previous version or whatever you need to do.
/*
/*When it comes to production, why the hell would you install 99% of extra
/*space taking codes
/*To: CF-Talk
/*Subject: Re: SVN in Production
/*
/*On Monday 11 Aug 2008, Andrew Scott wrote:
/* SVN SHOULD NEVER BE USED IN PRODUCTION...
/*
/*I assume you mean 'to deploy code to a production box' ?
/*Because as a production RCS it's well known for being utterly solid.
/*
/* When it comes
: Monday, 11 August 2008 7:29 PM
/*To: CF-Talk
/*Subject: Re: SVN in Production
/*
/*Kym Kovan wrote:
/* Looking at some of the responses in the recent thread on SVN v ftp I get
/* an impression that some folk are using SVN clients on Production boxes.
/* What are people's thoughts
Scott [mailto:[EMAIL PROTECTED]
/*Sent: Monday, August 11, 2008 6:52 AM
/*To: CF-Talk
/*Subject: RE: SVN in Production
/*
/*Kym,
/*
/*I was not responding to you directly, if I did not answer your question
/*then
/*let me ask you this.
/*
/*If you are tight for HD space, and not everyone is. But what
PROTECTED]
/*Sent: Monday, August 11, 2008 6:59 AM
/*To: CF-Talk
/*Subject: RE: SVN in Production
/*
/*Actually that's not entirely true
/*
/*And this is one reason I refuse to use subclipse
/*
/*What you don't see is the processes that can and do run in the background,
/*if you run eclipse
By committing and updating the file you changed. You don't have to
commit/update the entire site.
/*-Original Message-
/*From: Andrew Scott [mailto:[EMAIL PROTECTED]
/*Sent: Monday, August 11, 2008 7:09 AM
/*To: CF-Talk
/*Subject: RE: SVN in Production
/*
/*And how are you going
that is
regularly merged to multiple code sets, then write script you can run where
you can specify multiple source and destination file.
Eric
/*-Original Message-
/*From: Andrew Scott [mailto:[EMAIL PROTECTED]
/*Sent: Monday, August 11, 2008 6:57 PM
/*To: CF-Talk
/*Subject: RE: SVN in Production
that branch.
Eric
/*-Original Message-
/*From: Andrew Scott [mailto:[EMAIL PROTECTED]
/*Sent: Monday, August 11, 2008 7:58 PM
/*To: CF-Talk
/*Subject: RE: SVN in Production
/*
/*Sorry,
/*
/*Maybe I should have stated:
/*
/*Not even SVN can automatically decide what changes to make live and what
, August 11, 2008 8:05 PM
/*To: CF-Talk
/*Subject: RE: SVN in Production
/*
/*For FUCK sake.
/*
/*I never said anything about merging between SVN repositories.
/*
/*I fucking said merging code from dev - production, which has nothing to
/*do
/*with SVN what so ever that is my damn point.
/*
/*You
/*To: CF-Talk
/*Subject: RE: SVN in Production
/*
/*You have my curiosity now...
/*
/*Explain to me how, SVN automation is going to know that I have 4 changes
/*and
/*only 3 of these are going to need to go to production.
/*
/*Not that it is going to change for me, I need to log into a VPN
are unnecessary. If you add a developer to the mix, it is easy to break out
new branches to accommodate.
Eric
/*-Original Message-
/*From: Andrew Scott [mailto:[EMAIL PROTECTED]
/*Sent: Friday, August 15, 2008 10:56 PM
/*To: CF-Talk
/*Subject: RE: SVN in Production
/*
/*Yes, but can
whether that is a versioning system, coding styles, or whatever.
Eric
/*-Original Message-
/*From: Andrew Scott [mailto:[EMAIL PROTECTED]
/*Sent: Friday, August 15, 2008 11:07 PM
/*To: CF-Talk
/*Subject: RE: SVN in Production
/*
/*No I was not concerned about HD space, my view is simple
/*To: CF-Talk
/*Subject: RE: SVN in Production
/*
/*Ok,
/*
/*As you directed the response to me
/*
/*1) I am not worried about what you think, the reason being is that I have
/*clearly stated that on a few occasions everyone is different.
/*
/*2) Even when I did Coldfusion development full time
.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273
-Original Message-
From: Dana Kowalski [mailto:[EMAIL PROTECTED]
Sent: Friday, 15 August 2008 12:27 AM
To: CF-Talk
Subject: Re: SVN in Production
This thread is kind of heavy handed. My personal opinion with anything
Watson [mailto:[EMAIL PROTECTED]
Sent: Saturday, 16 August 2008 7:32 PM
To: CF-Talk
Subject: Re: SVN in Production
Andrew, your initial point (that you made redundantly clear by way of
caps and repetition) was to never use subversion to move code to
production. You then make your detailed case
1) I am not worried about what you think, the reason being is that I have
clearly stated that on a few occasions everyone is different.
Neither me you. You have clearly stated that everyone is different but
that no one should ever use SVN in production. I would like to know
the concrete reasons
Subject: Re: SVN in Production
On Tuesday 12 Aug 2008, Andrew Scott wrote:
There is a bug in Subclipse, that sees file saving take anything from an
extra 2mins upto hours
We use Subclipse here, and that simply does not happen. Our mileage clearly
varies.
--
Tom Chiverton
-Talk
Subject: Re: SVN in Production
On Tuesday 12 Aug 2008, Andrew Scott wrote:
Not even SVN can automatically decide what changes to make live and what
not to make live, between developer changes
I dunno, I've heard of systems which auto updated the live environment to
the
most recent tag which
to most, but it appeared not.
--
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273
-Original Message-
From: Dana Kowalski [mailto:[EMAIL PROTECTED]
Sent: Friday, 15 August 2008 12:27 AM
To: CF-Talk
Subject: Re: SVN in Production
On Tuesday 12 Aug 2008, Andrew Scott wrote:
There is a bug in Subclipse, that sees file saving take anything from an
extra 2mins upto hours
We use Subclipse here, and that simply does not happen. Our mileage clearly
varies.
--
Tom Chiverton
On Tuesday 12 Aug 2008, Andrew Scott wrote:
Please don't confuse the topic Tom, and twist what I am saying.
I seem to be having some difficultly with your points, so bear with me :-)
My point is very simple, so let me spell it out for you again.
When using export, that is not actually using
On Tuesday 12 Aug 2008, Andrew Scott wrote:
Not even SVN can automatically decide what changes to make live and what
not to make live, between developer changes
I dunno, I've heard of systems which auto updated the live environment to the
most recent tag which matches a patten (i.e.
This thread is kind of heavy handed. My personal opinion with anything like
this is your mileage will vary. There are simply too many factors to heavy hand
a this is the only way to do it. Everyones configurations, staff, resources,
technical knowledge etc etc vary. You use what works, simple
doesn't work.
--
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273
-Original Message-
From: denstar [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 12 August 2008 3:21 PM
To: CF-Talk
Subject: Re: SVN in Production - back to the original
Andrew Scott wrote:
Don't put words into my mouth.
I was not aware I did so. Perhaps you could quote me?
As for xml changes that are not related to your source code is generally
handled by daily backups anyway, and most people prefer that as it can put
the machine into a state quicker than
:-(
Took me to literal..
--
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273
-Original Message-
From: Jochem van Dieten [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 12 August 2008 4:17 PM
To: CF-Talk
Subject: Re: SVN
Brian Kotek wrote:
All of this can (and should) be automated with ANT. That means at the click
of my mouse I can execute the entire deployment process in exactly the same
way every single time. That might mean:
- Zip the current code, timestamp it, and copy it to a back folder for
easy
Andrew Scott wrote:
There is no way to automatically merge changes, I mean even SVN can't do
that between developers and its a manual process to update and merge
changes.
That is correct. Which is why it is a best practice to always tag your
code and deploy a tag. Deployment scripts should
Andrew Scott wrote:
Or in a more common example, as most Coldfusion developers are single team
developers. The client has requested a complete change to their system, when
finished he approved 60% of the changes and wants them to go live right now.
I can't just export now can I? So again I
On Mon, Aug 11, 2008 at 11:56 PM, Andrew Scott wrote:
:-( Yes, I understand about commit early and commit often. But I don't see
how that solves the problem? That really has nothing to do with branches,
though does it?
Well I guess a real-world example would be, what, 4 tickets, 3 of
which are
Sure, that makes perfect sense Jochem. I was just outlining how I've done
this and how I think most people would probably approach it. Obviously you
need to do it in the way that makes sense for your application and your
environment. Whatever the steps involved, the key is to make it as automatic
On Tue, Aug 12, 2008 at 3:29 AM, Jochem van Dieten
[EMAIL PROTECTED]wrote:
That is correct. Which is why it is a best practice to always tag your
code and deploy a tag. Deployment scripts should not do merging, they
should only deploy what has already been merged, tagged and tested.
Thanks,
You need to delete those SVN dir's with a script.
Hello,
Looking at some of the responses in the recent thread on SVN v ftp I get
an impression that some folk are using SVN clients on Production boxes.
What are people's thoughts on this? Is it a security risk, is it
dangerous in some other
You need to delete those SVN dir's with a script.
mbcomms
BTW: I still prefer using DIFF in combination with FTP... But I am a lonely
guy, if you search with deploy web app on google it's all SVN nowadays.
~|
Adobe®
SVN SHOULD NEVER BE USED IN PRODUCTION...
SVN is used to have a revision control system, so that you could roll back
to a previous version or whatever you need to do.
When it comes to production, why the hell would you install 99% of extra
space taking codes and indexes to a production server?
clear statement, I'll use that in my meeting with the boss :)
SVN SHOULD NEVER BE USED IN PRODUCTION...
SVN is used to have a revision control system, so that you could roll back
to a previous version or whatever you need to do.
When it comes to production, why the hell would you install 99% of
, 11 August 2008 7:04 PM
To: CF-Talk
Subject: Re: SVN in Production
clear statement, I'll use that in my meeting with the boss :)
SVN SHOULD NEVER BE USED IN PRODUCTION...
SVN is used to have a revision control system, so that you could roll back
to a previous version or whatever you need to do
Kym Kovan wrote:
Looking at some of the responses in the recent thread on SVN v ftp I get
an impression that some folk are using SVN clients on Production boxes.
What are people's thoughts on this? Is it a security risk, is it
dangerous in some other way, or is it a bad thing because of all
Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273
-Original Message-
From: Jochem van Dieten [mailto:[EMAIL PROTECTED]
Sent: Monday, 11 August 2008 7:29 PM
To: CF-Talk
Subject: Re: SVN in Production
Kym Kovan wrote:
Looking at some of the responses
On Monday 11 Aug 2008, Andrew Scott wrote:
SVN SHOULD NEVER BE USED IN PRODUCTION...
I assume you mean 'to deploy code to a production box' ?
Because as a production RCS it's well known for being utterly solid.
When it comes to production, why the hell would you install 99% of extra
space
Yes, indeed. With a diff ( I want to use free commander with Winmerge) tool,
you SEE the changes going live. I point that one out in a previous post.
I work on a large project in a existing application which I check-in constantly
(Backup purpose and team work) , but doesn't need to go live.
is when its test and ready as a release
candidate.
-Original Message-
From: Joeri B [mailto:[EMAIL PROTECTED]
Sent: 11 August 2008 10:58
To: CF-Talk
Subject: Re: SVN in Production
Yes, indeed. With a diff ( I want to use free commander with Winmerge) tool,
you SEE the changes going live
On Monday 11 Aug 2008, Andrew Scott wrote:
The latter should never be an issue, or even considered. Anyone who makes
changes to production and not in a development environment shouod be hung
out to dry or better still beaten with a stick until you realise that
development is what it means.
Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273
-Original Message-
From: Tom Chiverton [mailto:[EMAIL PROTECTED]
Sent: Monday, 11 August 2008 7:46 PM
To: CF-Talk
Subject: Re: SVN in Production
On Monday 11 Aug 2008, Andrew Scott wrote
then good luck to you.
--
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273
-Original Message-
From: Joeri B [mailto:[EMAIL PROTECTED]
Sent: Monday, 11 August 2008 7:58 PM
To: CF-Talk
Subject: Re: SVN in Production
Yes, indeed
Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273
-Original Message-
From: Robert Rawlins [mailto:[EMAIL PROTECTED]
Sent: Monday, 11 August 2008 8:09 PM
To: CF-Talk
Subject: RE: SVN in Production
This is an interesting conversation, I've been using
about it for a minute
--
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273
-Original Message-
From: Tom Chiverton [mailto:[EMAIL PROTECTED]
Sent: Monday, 11 August 2008 8:09 PM
To: CF-Talk
Subject: Re: SVN in Production
Andrew Scott wrote:
... snip If you
checkout it might be a copy of the current index from svn, but that is still
and let me repeat myself this is still double your storage space if in a
shared environment where space is an issue.
Andrew, that is a major step back from your earlier
You're an extremely aggressive individual aren't you Andrew?
-Original Message-
From: Andrew Scott [mailto:[EMAIL PROTECTED]
Sent: 11 August 2008 12:15
To: CF-Talk
Subject: RE: SVN in Production
DO NOT ASSUME WHAT I HAVE DONE OR NOT DONE
I have not only been there, but that was 10
Andrew Scott wrote:
I could create an image, this image could be used for 10 different sites and
slight changes to each version, but it is only relevant to one of my
clients. I would not be making that an export from SVN because you will end
up with images that do not belong to the project
On Monday 11 Aug 2008, Andrew Scott wrote:
If you feel it works for you then continue, but let me tell you this. Move
outside of coldfusion and use those same approaches you will be not only
scoldered. But I would say you might become an outcast to boot
I dunno, I bet the PHP folks are
On Monday 11 Aug 2008, Kym Kovan wrote:
intermediate server to import it into SVN and then checked it out to the
test server and then ran some file sync tools to the Production boxes
which are FTP distance away. It took over an hour to say no difference!
That's one of the great steps SVN
Kym,
I was not responding to you directly, if I did not answer your question then
let me ask you this.
If you are tight for HD space, and not everyone is. But what good would it
be too actually have .svn files on your production server? If it doesn't
need to be required to run, then it doesn't
PM
To: CF-Talk
Subject: Re: SVN in Production
Andrew Scott wrote:
I could create an image, this image could be used for 10 different sites
and
slight changes to each version, but it is only relevant to one of my
clients. I would not be making that an export from SVN because you will
end
up
much longer :-(
--
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273
-Original Message-
From: Tom Chiverton [mailto:[EMAIL PROTECTED]
Sent: Monday, 11 August 2008 9:38 PM
To: CF-Talk
Subject: Re: SVN in Production
On Monday 11
Tom Chiverton wrote:
On Monday 11 Aug 2008, Kym Kovan wrote:
intermediate server to import it into SVN and then checked it out to the
test server and then ran some file sync tools to the Production boxes
which are FTP distance away. It took over an hour to say no difference!
That's one of
PM
To: CF-Talk
Subject: Re: SVN in Production
Tom Chiverton wrote:
On Monday 11 Aug 2008, Kym Kovan wrote:
intermediate server to import it into SVN and then checked it out to the
test server and then ran some file sync tools to the Production boxes
which are FTP distance away. It took over
Andrew Scott wrote:
What
Do you mean by repo - server and server - repo?
The latter should never be an issue, or even considered. Anyone who makes
changes to production and not in a development environment shouod be hung
out to dry or better still beaten with a stick until you realise that
Andrew Scott wrote:
And how are you going to migrate small changes in a midst of other changes?
Good response Andrew to my question, just what I wanted. Unfortunately
your response is top-replied with your signature as well, with its
correct --, so in Thunderbird my question below that is
On Monday 11 Aug 2008, Andrew Scott wrote:
And this is one reason I refuse to use subclipse
will show you that svn can be contacted and updated without your knowledge,
how else do you know if there are changes to the code...
That's a good thing.
I want my RCS updated when I delete or
On Monday 11 Aug 2008, Andrew Scott wrote:
secure you have your code base open to the whole world when and if it is
hacked.
With the vast majority of ColdFusion deployments, that's the case anyway.
The default JRun connector for Adobe's engine still runs the .cfm files from
inside the .svn
I disagree completely. There's absolutely nothing wrong with using SVN in
production for deployment.
Beyond Compare? It's a great program...but using it to deploy code? The idea
makes me shudder. In fact, doing anything manual related to code deployment
makes me shudder.
There are easy ways
Kym Kovan wrote:
Yes, and that lends me to the thought that the best scenario for our
particular problem would be to have an exported copy on each production
box (yes, they are clustered) and use a standard diff tool from there to
flip the changes over to the actual production site.
I can
On Mon, Aug 11, 2008 at 5:25 AM, Kym Kovan wrote:
So our problem is how to push out changes to the Production boxes in a
sensible fashion and hence our question that has raised such ire amongst
one person at least :-)
I haven't been watching this thread too close, but...
SVN has
Message-
From: Jochem van Dieten [mailto:[EMAIL PROTECTED]
Sent: Monday, 11 August 2008 10:23 PM
To: CF-Talk
Subject: Re: SVN in Production
Andrew Scott wrote:
What
Do you mean by repo - server and server - repo?
The latter should never be an issue, or even considered. Anyone who makes
: Monday, 11 August 2008 11:05 PM
To: CF-Talk
Subject: Re: SVN in Production
Andrew Scott wrote:
And how are you going to migrate small changes in a midst of other
changes?
Good response Andrew to my question, just what I wanted. Unfortunately
your response is top-replied with your signature
. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273
-Original Message-
From: Tom Chiverton [mailto:[EMAIL PROTECTED]
Sent: Monday, 11 August 2008 11:46 PM
To: CF-Talk
Subject: Re: SVN in Production
On Monday 11 Aug 2008, Andrew Scott wrote:
And this is one reason I
: Monday, 11 August 2008 11:54 PM
To: CF-Talk
Subject: Re: SVN in Production
On Monday 11 Aug 2008, Andrew Scott wrote:
of dev - QA - production and then at least, once made live if the
changes
Uh huh. We then use SVN make sure what was QA'ed and tested is exactly the
same as what was deployed
Don't put words into my mouth.
I don't see anyone putting words into your mouth. Jochem simply mentioned
that some people use revision control systems for things other than
application source code. That is certainly true, even if you don't do that
yourself.
As for xml changes that are not
: SVN in Production
I disagree completely. There's absolutely nothing wrong with using SVN in
production for deployment.
Beyond Compare? It's a great program...but using it to deploy code? The idea
makes me shudder. In fact, doing anything manual related to code deployment
makes me shudder
but is not ideal to about 98% of
people.
--
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273
-Original Message-
From: denstar [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 12 August 2008 7:36 AM
To: CF-Talk
Subject: Re: SVN
Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 12 August 2008 10:12 AM
To: CF-Talk
Subject: RE: SVN in Production
Don't put words into my mouth.
I don't see anyone
On Mon, Aug 11, 2008 at 6:09 PM, Andrew Scott wrote:
Brian...
A statement like this means you are not very good at your job.
Hey, we're all learning and whatnot, Andrew, cut the man some slack! :-)
There is no way to automatically merge changes, I mean even SVN can't do
that between
-Original Message-
From: Brian Kotek [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 12 August 2008 12:01 AM
To: CF-Talk
Subject: Re: SVN in Production
I disagree completely. There's absolutely nothing wrong with using SVN in
production for deployment.
Beyond Compare? It's a great program...but using
On Mon, Aug 11, 2008 at 5:56 PM, Andrew Scott wrote:
Kym,
Think of an Application has being something that more than one client could
have. Then think about their requirements, and how it might differ to
another client.
I'm not sure if I should go into it, but-- You're doing it wrong.
Don't quote something out of context.
I deliberately removed that before replying, so you assumed
that I was talking about that now? I am well aware what SVN
is, and anyone who has read the documentation would know that
without a doubt now wouldn't they?
I don't see any reason to doubt
On Mon, Aug 11, 2008 at 8:23 PM, denstar [EMAIL PROTECTED] wrote:
On Mon, Aug 11, 2008 at 6:09 PM, Andrew Scott wrote:
Brian...
A statement like this means you are not very good at your job.
Hey, we're all learning and whatnot, Andrew, cut the man some slack! :-)
Thanks Den. :-)
But
: Tuesday, 12 August 2008 10:23 AM
To: CF-Talk
Subject: Re: SVN in Production
On Mon, Aug 11, 2008 at 6:09 PM, Andrew Scott wrote:
Brian...
A statement like this means you are not very good at your job.
Hey, we're all learning and whatnot, Andrew, cut the man some slack! :-)
There is no way
On Mon, Aug 11, 2008 at 6:44 PM, Brian Kotek wrote:
On Mon, Aug 11, 2008 at 8:23 PM, denstar wrote:
Hey, we're all learning and whatnot, Andrew, cut the man some slack! :-)
Thanks Den. :-)
But believe me, you don't have to defend me to Andrew. At all.
Oh, snap! =] Didn't mean to imply
On Mon, Aug 11, 2008 at 6:58 PM, Andrew Scott wrote:
Not even SVN can automatically decide what changes to make live and what
not to make live, between developer changes
If you've got things organized the right way, it's pretty easy. You
do need to make use of tags and revision numbers
Kotek [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 12 August 2008 10:34 AM
To: CF-Talk
Subject: Re: SVN in Production
I never said you would automatically handle merge changes. If you are
merging, then you do that in the repository and tag the merged file set
before you perform the deployment. That has
-
From: denstar [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 12 August 2008 10:35 AM
To: CF-Talk
Subject: Re: SVN in Production
On Mon, Aug 11, 2008 at 5:56 PM, Andrew Scott wrote:
Kym,
Think of an Application has being something that more than one client
could
have. Then think about
]
Sent: Tuesday, 12 August 2008 10:44 AM
To: CF-Talk
Subject: RE: SVN in Production
Don't quote something out of context.
I deliberately removed that before replying, so you assumed
that I was talking about that now? I am well aware what SVN
is, and anyone who has read the documentation would
Lighten up Andrew. You have been in attack mode from your first response.
It is obvious you have strong opinions on the topic, but responding like
you have been does nothing to educate the people here who may not have
an opinion yet and are trying to learn something from these threads.
Andrew
-Original Message-
From: denstar [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 12 August 2008 11:03 AM
To: CF-Talk
Subject: Re: SVN in Production
On Mon, Aug 11, 2008 at 6:58 PM, Andrew Scott wrote:
.
As stated, if I have 2 changes one has to go live and the other is not
ready. Another
Maybe I am not understanding you now.
At this point, perhaps neither of us is making much sense to the other right
now. This is my signal to take the rest of the night off!
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
Fig Leaf Software provides the highest caliber
Andrew Scott wrote:
You have my curiosity now...
Explain to me how, SVN automation is going to know that I have 4 changes and
only 3 of these are going to need to go to production.
Andrew, I think the point being made is that if you have 4 changes they
should be in 4 branches or something
To: CF-Talk
Subject: Re: SVN in Production
Andrew Scott wrote:
You have my curiosity now...
Explain to me how, SVN automation is going to know that I have 4 changes
and
only 3 of these are going to need to go to production.
Andrew, I think the point being made is that if you have 4 changes
It seems I started something by asking if I was understanding some
folk's practices correctly. Actually I just asked a question, someone
else started something :^)
Meanwhile I filled in a few details of an issue we have with this new
client need with their monster site and in amongst all of
Andrew Scott wrote:
Kym,
Which is why I painted the scenario of this, and I will repeat it again
because it seems to be getting lost in translation.
yes, yours Andrew. The original question came up because you stated that
you could not send out 3 of 4 changes. In one of the many replies
.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273
-Original Message-
From: Brian Kotek [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 12 August 2008 10:34 AM
To: CF-Talk
Subject: Re: SVN in Production
I never said you would automatically handle merge changes. If you are
merging
that the minimal the better.
--
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273
-Original Message-
From: Kym Kovan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 12 August 2008 12:52 PM
To: CF-Talk
Subject: Re: SVN in Production
On Mon, Aug 11, 2008 at 7:27 PM, Andrew Scott wrote:
You have my curiosity now...
Explain to me how, SVN automation is going to know that I have 4 changes and
only 3 of these are going to need to go to production.
Kym pretty much explained what I was getting at, changing your style.
There's
With gigs of data, and it's possible, something incremental seems like
a good idea.
A nice bit about SVN (and some other version control systems) is the
binary difference stuff, so only the changes are transmitted, not the
entire file. Sweet for large data files, neh?
I'm thinking a nice setup
Message-
From: denstar [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 12 August 2008 2:29 PM
To: CF-Talk
Subject: Re: SVN in Production
On Mon, Aug 11, 2008 at 7:27 PM, Andrew Scott wrote:
You have my curiosity now...
Explain to me how, SVN automation is going to know that I have 4 changes
and
only
99 matches
Mail list logo
