I don't reckon this thread is long enough yet, so here's some more... There are so many ways to use Subversion that it's easy to be in violent agreement. We all agree on this:
Don't break <the build>. Make sure you thoroughly test before you <commit>. And be sure to <backup> your working copy. But we interpret the <> words differently: Andrew: the build = the latest revision Tom: the build = the approved tag Me: the build = the latest revision from trunk Andrew: commit = the usual subversion commit Tom: commit = create an approved tag Me: commit = merge my personal dev branch into trunk Andrew: backup = filesystem backup of working copy Tom: backup = commit working copy into repo, then backup repo Me: backup = commit working copy into my dev branch of the repo, then backup repo And thereby end up with three different procedures that look different but in fact do the same thing (maybe with slightly different emphases). We all create abstractions for a living here, surely we can cope with that. Jaime Metcher > -----Original Message----- > From: Andrew Scott [mailto:[EMAIL PROTECTED] > Sent: Saturday, 12 May 2007 3:00 AM > To: CF-Talk > Subject: Re: Subversion Tutorial Posted > > > So what your saying is this. > > You and I are on the same team working on the same project.... > > I make some changes to my code, and I have not written any TDD test cases > and just submit my work into subversion and go home, while I am travelling > home I am involved in a car accident and put into hospital and > out of action > for a day or 2... Thanking god its not serious... > > Anyway, the code that I submitted broke the website / application > in a major > way. now its your Job or someone elses to step through the > revisions to see > what I did to break the code. Now on top of this, you have one hour to > figure this out before you demostrate the new changes that had > been made for > the last few weeks. > > However I can't be contacted cause I am still not very > coheriant.... But due > to an unforseen problem, I not only broke the latest version > (Note: version > not revision) and forced others to waste time finding out what I did to > break the latest build / code. In the meantime the client is > being patient, > and you have to put him/her off for a day or two to get this sorted out, > then he begins to wonder what he/she has paid for and is > becomming a little > impatient with you. > > Are you begining to understand my point now, it doesn't matter what you > think in the long run you might have saved more time on the > project if I did > not commit this code and stopped everyone else from getting their > job done. > > Subversion is a version control system, with the ability to handle > revisions. It is not a revision control system and should not be treated > that way. The mentality of a developer should be take action against all > possible problems, and if my code is going to break the latest > build at the > 11th hour or not I shouldn't commit it until I am 100% happy with the fact > all my unit test cases have passed and I have covered 100% of code in my > tests. > > Bobby, your methods might work. But it can be improved and thats what I am > trying to say to you, why do you think the java community adopted > the agile > and TDD aproach, and use subversion for what it is designed for. They know > at the end of the day they can export the code to a test server, > and its as > stable as it should be for any demo or presentation at the drop of a hat. > > > On 5/12/07, Bobby Hartsfield <[EMAIL PROTECTED]> wrote: > > > > > Its your time your wasting > > > > I'm not wasting any time or money but thanks for your concern. I have a > > pretty good reputation for OVER delivering applications WELL > under budget > > AND deadline. Anyone who has worked with me can vouch for that. I also > > come > > from a place where I clean up after myself. If I spill it, I'll clean it > > up... If I break it, I'll fix it. I don't depend on other developers to > > hold > > my hand and fix mistakes that I might have made. I would do > that on my own > > time and dime. If I had back every dollar I've 'wasted' doing > so over the > > years, I MIGHT be able to buy you a beer. Maybe, over that beer, I could > > explain to you the concept of "agree to disagree" and the definition of > > narcissism. > > > > No virus found in this outgoing message. > > Checked by AVG Free Edition. > > Version: 7.5.467 / Virus Database: 269.6.8/797 - Release Date: 5/10/2007 > > 5:10 PM > > > > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJP Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:277890 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
