Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornellcs!newsstand.cit.cornell.edu!news.sprintlink.net!newsfeed.internetmci.com!in2.uu.net!news.new-york.net!ritz!jpletzke
From: jpletzke@ritz.mordor.com (Jonathan Pletzke)
Subject: Source code/Repository management
Organization: Mordor International
Date: Fri, 29 Dec 1995 20:42:44 GMT
X-Newsreader: TIN [version 1.2 PL2]
Message-ID: <DKD879.J5L@ritz.mordor.com>
Lines: 28

Much of my time is spent worrying about the best way to manage smalltalk 
source code created by development teams.  This issue is not unlike 
managing any other group development effort, as I experienced when 
developing with C and C++.

My opinion is that:
1. Everything stored should be source code.
2. A regular re-build of the entire system from source should be done.
3. Each developer should upgrade to the latest build after it has been tested
4. Test code should be written for each class and group of classes in the 
entire system by the class authors, and executed each time before the 
code is committed to the repository, and after the integration has been done.
5. Each class and method should be fully commented, including a class 
method called COMMENT or NOTES that answers a string describing the class 
and all instance variables, and a method comment in each method that 
declares public or private, expected return value, and function of the 
method.

Does anyone do this?
I have done this in C/C++, but have encountered resistance from 
Smalltalkers who would prefer to trade file-ins, ad-hoc test items, 
object files (BOSS or ObjectFiler), or an entire image.  I believe that 
this is due in part to the personal nature of Smalltalk develpment, but 
find that it can be counter productive to delivering quality code.

Any thoughts?

-Jonathan
