Question is about organizing dev environment for the web development.
- There is 2 things to deploy: web site and database schema
- We use SVN to keep track of source code
- We use RedGate tools to generate migration SQL and to version-control database schema.
- It is important to have fresh copy of data in our dev environment.
At first, we just worked each in personal databases. Now our team getting bigger so we have dev server with shared database.
For customer, we created "test" website that we run on our server. And it points to our dev database.
For data - we bring fresh copy of database weekly, so it's just another PITA because we do it by backup/restore and obviously schema different when we bring it back.
Where we have problem now is when we release something for customer to test. They check, it may take some time. By the time they check we might already have some other new features added to TEST site. Now, let's say production missing A, B, and C features. Customer tested A, but B and C need to be tested or changed. A need to go to release.
In big companies were I worked there was DEV, TEST and PROD environments. Pretty much DEV->TEST didn't go unless TEST->PROD happened. This caused just wasted time (realistically). Now we can't afford just sitting, so how do we work fast-paced like this with minimum hickups.
Now because we still waiting from a customer on feedback on "A" - we already "forgot" what else we added. With many people it just get's more complex.
So, I guess question is: How to manage DB/Code version control and separate features publishing in such environment? With minimal bureaucracy.