Re: Shouldn't WDSC include SCM?

[Vernon Hamberg <vhamberg@xxxxxxxxxxx>]

Joe

Seems there are a couple things that do what you want already - I've 
seen a system at one of our customers, don't know who makes it or if 
it's from Midrange Computing or NEWS/400

And if you followed the companion thread - Richard and Aaron are 
conspiring for something with SVN - now if we can add object 
relations to their concepts (big hint, boss!!!).

Regards
Vern

At 03:50 PM 12/1/2007, you wrote:

> ----- Original Message -----
> From: "David Gibbs" <david@xxxxxxxxxxxx>
> Subject: Re: Shouldn't WDSC include SCM?
>
>
> >> Sounds like an opportunity for a new SCM vendor to enter the scene...
> >> Or, perhaps this could be a community project and offered as open
> >> source (courtesy of midrange.com)....
> >
> > Sadly, I'm afraid I can't do that.  There is a small mater of conflict
> > of interest.
>
> Given your conflicting position, maybe you could make the case with your
> team about the need to a package that suits the small shops too?
>
> As much as I liked working with change management (Turnover) in a prior
> life, we would never be able to justify the cost for our 3 man shop.  And in
> many (most) ways it would be overkill.
>
> I would be happy with a 'Source Control Manager' that simply did two things:
> 1 - Allow source to be checked in/locked & checked out/unlocked by developer
> with change notes
> 2 - Maintain a revisions library to allow us to see prior copies
>
> I just want to avoid source code contention and have a complete history.
>
> It is something we would pay for from a vendor, or contribute to the design
> and coding of if it were an open source project.
>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.