Manual code management practices
Guy Werry
guy.werry@hbms.ca
Thu, 19 May 2005 07:35:15 -0500
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C55C6F.3570FE50
Content-Type: text/plain;
charset="iso-8859-1"
If you're on Unix, then use RCS. It's embedded in the OS, no cost.
It keeps a history of each revision, and shows WHO has checked out a
particular version. Unless you're using generic logons, this works quite
well.
It also has tools that help manage multiple developers, although we don't
use these here, as we stay away from that scenario (small shop, which
helps). As a side note, RCS works on any language, even scripts.
Automate as much as possible!
The idea about regular meetings is a very sound one. A half-hour a day or
every 2nd day will pay HUGE dividends. Really, though, this work should be
planned, so everyone knows who is working on what and when.
Hope this helps .....
Guy L. Werry
Senior Systems Analyst
Hudson Bay Mining & Smelting Co., Limited.
-----Original Message-----
From: Olmos, Fernando (Sericon at Alcoa)
[mailto:Fernando.Olmos@alcoa.com.au]
Sent: Wednesday, May 18, 2005 6:36 PM
To: powerh-l@lists.sowder.com
Subject: Manual code management practices
Hi everyone.
I recently re-joined the PH list due to a larger than expected volume of
work requiring my PH skills.
Just one question, which is baffling a lot of my clients at the moment.
Code management:
* What practices are being used?
* What tools are being used?
* Any DOs and DONTs?
My client is running Powerhouse, in a HP9000 Unix box, and has recently
hired a few contractors and myself to do some work which will require us to
share code, and keep it all seamless without people overwriting other
people's work.
Currently we use a "repository" method which is to keep the code in a
central location and ONLY pull it out of there if the file is not listed in
a "holding location" elsewhere. If the code is in the holding location then
it means someone is using it, and so the developer has to email/communicate
with the team to find out who is using it, why and discuss how to "share"
the program.
Unfortunately with this system, as you all know, it's heavily reliant on
human "good will" and control. If someone forgets to pull out the source
code from the holding area or at least comment it to say this is no longer
required, then other developers will be wasting time chasing people or
making assumptions (because some people just don't like to talk!) and start
using the program anyway.
Is there a manual system that is better than the above? We are trying to
stay away from using specific code management tools like CM or VSS due to
cost and timing spent on installation, training, management, etc.
Thanks guys.
Fernando J. Olmos
Melbourne
+61 3 9629-9444
Software Consultant (Information Services - Alcoa Australia)
------_=_NextPart_001_01C55C6F.3570FE50
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Manual code management practices</TITLE>
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=062412812-19052005>If
you're on Unix, then use RCS. It's embedded in the OS, no
cost.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=062412812-19052005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=062412812-19052005>It
keeps a history of each revision, and shows WHO has checked out a particular
version. Unless you're using generic logons, this works quite well.
</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=062412812-19052005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=062412812-19052005>It
also has tools that help manage multiple developers, although we don't use these
here, as we stay away from that scenario (small shop, which helps). As a
side note, RCS works on any language, even scripts.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=062412812-19052005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=062412812-19052005>Automate as much as possible!</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=062412812-19052005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=062412812-19052005>The
idea about regular meetings is a very sound one. A half-hour a day or
every 2nd day will pay HUGE dividends. Really, though, this work should be
planned, so everyone knows who is working on what and when.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=062412812-19052005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=062412812-19052005>Hope
this helps .....</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=062412812-19052005>
<P><FONT size=2>Guy L. Werry<BR>Senior Systems Analyst<BR>Hudson Bay Mining
& Smelting Co., Limited. </FONT></P></SPAN></FONT></DIV>
<BLOCKQUOTE>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Olmos, Fernando (Sericon at
Alcoa) [mailto:Fernando.Olmos@alcoa.com.au]<BR><B>Sent:</B> Wednesday, May 18,
2005 6:36 PM<BR><B>To:</B> powerh-l@lists.sowder.com<BR><B>Subject:</B> Manual
code management practices<BR><BR></FONT></DIV><!-- Converted from text/rtf format -->
<P><FONT face=Arial size=2>Hi everyone.</FONT> </P>
<P><FONT face=Arial size=2>I recently re-joined the PH list due to a larger
than expected volume of work requiring my PH skills.</FONT> </P>
<P><FONT face=Arial size=2>Just one question, which is baffling a lot of my
clients at the moment.</FONT> </P>
<P><FONT face=Arial size=2>Code management:</FONT> </P>
<UL>
<LI><FONT face=Arial size=2>What practices are being used?</FONT>
<LI><FONT face=Arial size=2>What tools are being used?</FONT>
<LI><FONT face=Arial size=2>Any DOs and DONTs?</FONT> <BR></LI></UL>
<P><FONT face=Arial size=2>My client is running Powerhouse, in a HP9000 Unix
box, and has recently hired a few contractors and myself to do some work which
will require us to share code, and keep it all seamless without people
overwriting other people's work.</FONT></P>
<P><FONT face=Arial size=2>Currently we use a "repository" method which is to
keep the code in a central location and ONLY pull it out of there if the file
is not listed in a "holding location" elsewhere. If the code is in the holding
location then it means someone is using it, and so the developer has to
email/communicate with the team to find out who is using it, why and discuss
how to "share" the program.</FONT></P>
<P><FONT face=Arial size=2>Unfortunately with this system, as you all know,
it's heavily reliant on human "good will" and control. If someone forgets to
pull out the source code from the holding area or at least comment it to say
this is no longer required, then other developers will be wasting time chasing
people or making assumptions (because some people just don't like to talk!)
and start using the program anyway.</FONT></P>
<P><FONT face=Arial size=2>Is there a manual system that is better than the
above? We are trying to stay away from using specific code management tools
like CM or VSS due to cost and timing spent on installation, training,
management, etc.</FONT></P>
<P><FONT face=Arial size=2>Thanks guys.</FONT> </P>
<P><SPAN lang=en-us><FONT face=Script color=#0000ff size=6>Fernando J.
Olmos</FONT></SPAN> <BR><SPAN lang=en-us><FONT face="Arial Narrow"
color=#008080 size=2>Melbourne</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face="Arial Narrow" color=#008080 size=2>+61 3 9629-9444</FONT></SPAN>
<BR><SPAN lang=en-us><FONT face="Arial Narrow" color=#800000 size=2>Software
Consultant (Information Services - Alcoa Australia)</FONT></SPAN>
</P><BR></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C55C6F.3570FE50--