On 2/23/06, Philip Hallstrom <subversion@philip.pjkh.com> wrote:
> > On 2/23/06, Philip Hallstrom <subversion@philip.pjkh.com> wrote:
> >> Mostly it comes down to knowing the designers and I just don't think
> >> they'd do it. And if they won't do it, then svn won't get used. And my
> >> life will be miserable :-)
> >
> > Most people won't do "different" or "extra" things if they don't have
> > to - it's human nature. Make svn part of the required process - their
> > changes *can't* get into <environment> without being in svn and you
> > basically force the issue.
> >
> > Maybe let them have a "playground" environment for them to do the
> > pixel-nudging work, but if they want to get integrated with the rest
> > of the build, they have to use svn? And cut off access to the rest of
> > the build by any means other than svn.
>
> Yep. That's part of the plan. Each of us will have our own vhost. Do
> whatever you want. But to get it into the QA vhost it's got to come from
> svn...
>
> I just don't want to completely change their habits right off the bat if I
> doin't have to :)
I say treat it like a Band-Aid - just do it. It'll hurt less than
inch by inch. :)
In all seriousness, are you able to present them with a case study or
some kind of demo showing them how much better off they'll be for
falling in line with all this?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 23 19:18:25 2006