Deployment Strategies
Brian Vallelunga <[email protected]>
| Newsgroups | gmane.comp.windows.devel.dotnet.web |
|---|---|
| Message-ID | <[email protected]> |
I'm being put in charge of a fairly good sized web site and a small team of developers. I'm trying to develop a strategy for organizing the submission of new web site code and content and then distribution to the live site. I'm curious what other people have found as best practices in these areas. We have a staging server and are currently using Vault as our source code repository. Right now we're using ASP.NET 1.1, but will be moving to 2.0 in the near future. This brings with it another set of questions. I've had quite a bit of experience developing sites, but generally with only one or two people at a time. Now we're likely to have four or five managing the content. It's also not likely we'll have set releases, but instead will have to be dealing with small changes occurring frequently and in different parts of the page. So what do people do in this sort of situation? How do you get your files where they need to be without having everyone step on each other's toes? Thanks, Brian =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com