RE: Turnover Config Question

["Bonnie Lokenvitz" <BLokenvitz@xxxxxxxxxx>]

No concurrent development here just an upgrade using the same
development library.  

Thank you,
Bonnie Lokenvitz
  Technology Consulting Inc.
  Sr. Technical Consultant
  320.679.8202

 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Friday, November 09, 2012 11:10 AM
To: Midrange Systems Technical Discussion
Subject: Re: Turnover Config Question

*** NOTE: I do not know much about Turnover and I _DO_ work for PTC
(formerly MKS) on the Implementer product.

On 11/9/2012 11:04 AM, Bonnie Lokenvitz wrote:
> I am working with a new client who uses Turnover.  Their configuration

> is letting multiple developers check out the same source member with 
> no error message and no halt.

This isn't necessarily a bad thing ... under certain circumstances you
might want to let multiple developers checkout the same source at the
same time.

As long as the code is checked out to different locations, this is known
as concurrent development (at least that's what we call it in
Implementer).

Properly managed, this can provide good productivity gains.

The key is to make sure that concurrent development is closely managed
and that changes made by one developer are merged in with changes made
by other developers.

david


--
IBM i on Power Systems - For when you can't afford to be out of business

I'm riding 100km (62 miles) in the 2013 Chicago Area Tour de Cure to
raise money for Diabetes research and education!  Sponsor me by visiting
http://archive.ridewithdavid.com.  Thanks!
--
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.