sounds familiar, where do you work? hehe! Yeah, after using CVS on my own ( well I cajoled maybe 2 others after a bit) within a team of non-cvs users for the past two years I finanlly just said everyone has to use it. Being the production owner gave me some leverage. "Use CVS or your code does not go to production" I said. :) I set them up with TortoiseCVS. It is uber simple to use. Only thing that wil lbe difficult is branching/merging...another day for that.
DK On 9/8/05, Anthony Prato <[EMAIL PROTECTED]> wrote: > I am pretty set on subversion already, my problem's been getting the > developers to break their bad habits. The process here seems to be > someone talks about a bug or something they don't like. A programmer > jumps on it with very little planning and starts coding. They think it > works, through it into production. I can't tell you how bad my stomach > turns when they say "lets just see what breaks" when referring to > putting things in production. And unfortunately these habits aren't > yet seen as problems by management either. I know its not pretty but I > need something for damage control until I can get a handle on things > here. > > :( > > > > On 9/8/05, Barney Boisvert <[EMAIL PROTECTED]> wrote: > > You can set up Subversion with Apache and access it over webDAV, which > > is really slick. Best of all, you can use both Subversion clients > > (that understand the SVN extensions to webDAV), and normal webDAV > > clients. For normal clients, Subversion will just do a commit for any > > files saved to the folders, giving entirely transparent versioning. > > If you've got a Subversion client, then you can do all the other stuff > > like pull revision histories. > > > > It's really a very elegant setup; the Subversion guys definitely got > > their stuff together. > > > > cheers, > > barneyb > > > > On 9/8/05, Anthony Prato <[EMAIL PROTECTED]> wrote: > > > I was hoping to hear what the list thinks on an issue I have. > > > I'm trying to make a number of changes at the place I've been working > > > for a few months. The small group of programmers has a disorganized > > > development process. I'm trying to work in some standard source > > > control but until that point I want to at least be able to, when > > > tracking bugs, to find out what changes where made to a file and when. > > > Backups somewhat help but what would be really nice is, like source > > > control, if I could look at the revision history for a single file. Is > > > there some sort of way to point a utility at a directory and have it > > > automatically check in files as they change on the server? (I know, > > > event gateways, but we don't have enterprise) The easier to install > > > and config the better. > > > > > > Anthony > > > > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:217661 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
