RE: Re: IIS Website versioning
From: Jeff Cave <jeff.cave_at_sunergon.com>
Date: 2004-04-21 17:31:53 CEST
-----Original Message-----
> The problems I see for something like that are more administrative than
I agree that this has huge potential for problems, but I think the scenario I have here will help avoid that.
This is a branch product off of our main product line. Essentially a customer buys our software and markets it as part of the service to their customer. One of our larger customers has asked for the product, but heavily customized. They want their own unique version of the product that they can market seperately from us.
Currently there are only a few "special" users that have access to the test site (several managers at various levels). These individuals are responsible for ensuring that we get their business process right, as well as getting a general feel for the impression from users in their area. The people using the test system are already in direct contact with the development team. I *do* want these users to see the changes as soon as they happen so that they are not calling asking where *their* particular issue is. That is really annoying when it has already been fixed, but hasn't been released to the test site.
I'm hoping that the only fixes applied directly to the head branch will be minor, and that branching will hide the big stuff from the client until it is ready for testing.
> AFAIK, the folder locking problem is a problem with IIS, and has nothing to
I'll try it, if it bombs horribly, I'll let you know.
Thanks to everyone for their input on this.
---------------------------------------------------------------------
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.