In a 'prior life' we managed exactly what you want in a 3 man shop with
these rules:
1) No source is ever modified in the production library
2) In the test library (ALL source being worked on was in
there-programmers had their own test object and data libraries) the last
three characters of the text description contained the programmers
initials who checked it out. If you need to work on it simply as them if
where they are on their changes. Often we found they checked out the
source but hadn't started on it yet or they were all done just waiting to
move back to production. There was little conflict.
3) We used TAATOOL Source Archive to capture changes that got moved into
production and also archived test multiple times per day just to have
checkpoints for when we did something 'stoopid'.
Doesn't meet any SOCKS or change control rules at all but it's simple and
Larry Bolhuis IBM Certified Advanced Technical Expert -
System i Solutions
Vice President IBM Certified Systems Expert:
Arbor Solutions, Inc. System i Technical Design and
Implementation V5R4
1345 Monroe NW Suite 259 eServer i5 iSeries LPAR Technical
Solutions, V5R3
Grand Rapids, MI 49505 IBM Certified Specialist
System i Integration with BladeCenter
and System x V1
(616) 451-2500 System i IT Simplification: Linux
Technical V5R4
(616) 451-2571 - Fax iSeries System Administrator for OS/400
V5R3
(616) 260-4746 - Cell
If you can read this, thank a teacher....and since it's in English,
thank a soldier.
"Porterfield, Sean" <sporter@xxxxxxxxxxxx>
Sent by: midrange-l-bounces+lbolhuis=arbsol.com@xxxxxxxxxxxx
12/03/2007 08:22 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc
Subject
RE: Shouldn't WDSC include SCM?
From: Joe D
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.
I'm not sure what your budget is, and I know that MKS Implementer does
more than what you requested, but I seem to recall that it was not
extremely expensive if you only wanted change management. It was
certainly the lowest quote we got when comparing "the big 3".
--
Sean Porterfield
This email is confidential, intended only for the named recipient(s) above
and may contain information that is privileged. If you have received this
message in error or are not the named recipient(s), please notify the
sender immediately and delete this email message from your computer as any
and all unauthorized distribution or use of this message is strictly
prohibited. Thank you.
midrange.com
