I'm sorry to be a pain. I guess it's that I've been a CVS user for so
many years; and I'm stuck in the CVS paradigm.
It often takes a two-by-four to get one to think out of the old box.
I'm going to have to "rethink" the SCM model that I'm used to... in
light of what I have heard.
I've been trying to use some of the Patterns found in Brad's book:
"Software Configuration Management"... I guess I need to give that book
a hard re-read.
Stephen McConnell
--- Mark Phippard <MarkP@softlanding.com> wrote:
> Stephen McConnell <mcconnell_stephen@yahoo.com> wrote on 01/13/2005
> 02:56:49 PM:
>
> > I appreciate the article...
> >
> > None of what anyone has said seems to help, though... there is a
> lot of
> > abstract stuff, but I have been given the responsibility of
> > implementing one of the most hairbrained configuration management
> > systems I've ever seen. They want to be all things to everyone.
>
> You mentioned that developers tell you about specific items to
> "promote".
> If that is the case, couldn't they just tell you specific revision
> numbers? Then you could use standard branches for your "areas" and
> use
> the relatively easy technique of merging specific revisions to a
> branch.
> This is essentially how Subversion handles their point releases.
> Specific
> revisions are nominated for backport, and if approved they are merged
> and
> integrated with the branch.
>
> It is fairly labor intensive, but it seems to match the model you
> described.
>
> Mark
>
>
>
_____________________________________________________________________________
> Scanned for SoftLanding Systems, Inc. by IBM Email Security
> Management Services powered by MessageLabs.
>
_____________________________________________________________________________
>
=====
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 13 22:02:19 2005