[thelist] Versioning best practices

Chris Johnston fuzzylizard at gmail.com
Thu Oct 28 09:35:48 CDT 2004


On Thu, 28 Oct 2004 00:38:50 -0400, Michael Robertson
<mike at mikeemedia.com> wrote:
> Greetings
> 
> We build and maintain a few different web applications that are
> frequently updated, customized or repaired. I'm looking for insight into
> anyones experience with processes for moving builds from a development
> environment to a production environment.
> 
> We're considering using a development server, staging server and a
> production server and moving new builds from staging to production once
> a week.
> 

Whatever you do, I would suggest two things:
1. document what you do and set up guidelines that dictate how and
when something is moved
2. restrict the people who have access to each server. This means that
the majority of people have access to the development server, fewer
people have access to the testing server, and only a few people have
access to the production server.

Also, you might want to think about setting up some kind of CVS server.


-- 
chris johnston

www.fuzzylizard.com

"For millions of years, mankind lived just like the animals and
something happened which unleashed the power of our imagination, we
learned to talk."
Pink Floyd


More information about the thelist mailing list