Really? Was it a problem with people trying to either 1) commit changes at the same time, or 2) commit changes that other users had made? Remember, in this scenario, there is only 1 copy of the source, on the network share.
On Tue, Nov 1, 2011 at 8:10 PM, Stevi Deter <[email protected]> wrote: > I know it's not what all the cool kids are using these days, but I've had > excellent success using SVN in similar situations. > > Heck, I've even managed to get database devs to check their code into SVN. > > -Stevi > > > > On Tuesday, November 1, 2011, Jeff Schumacher <[email protected]> > wrote: > > So imagine there is a team that has an old sckool setup, where there are > multiple developers working on the same copy of source code that exists out > on a network share. Also say that this application could be ASP.NET, > Classic ASP, or even PHP. The company only has 3 developers, and they > rarely run into either other. One person is responsible for rebuilding the > application, and this practice has been working for this team for years. > They get stuff accomplished, and that is key. They do not run local copies > of the application due to various reasons (this is not the point I'm trying > to argue, as I don't agree with this setup). This team also learned a long > time ago that backups are critical, so they have an automated system on > this network share that detects file changes and makes a archived, > timestamped, copy of the time. It's basically a rudimentary source control > system. > > > > Now, this team knows that they need to get with the times and use a > proper SCM, and they would also like to link their commits with their bug > tracking system, which happens to be Jira. So the question is, what SCM do > you think would work in their current shared source base setup, and why? I > have my opinion on which SCM I think might work, but rather than taint > suggestions, I'll leave my opinion out for the moment. > > > > > > Jeff > > > > -- > > You received this message because you are subscribed to the Google > Groups "Seattle area Alt.Net" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > [email protected]. > > For more options, visit this group at > http://groups.google.com/group/altnetseattle?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Seattle area Alt.Net" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/altnetseattle?hl=en. > -- (◣_◢) -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
