[Insight-developers] Creating a Draft directory for Code

[Joshua Cates]

An option for risky modifications to code already in the repository is to
branch an experimental revision from the main CVS tree.  The experimental
development would then not disturb the main developmental "trunk".  This
process is described in the CVS man pages.

Josh.
______________________________
 Josh Cates			
 School of Computer Science	
 University of Utah
 Email: cates@cs.utah.edu
 Phone: (801) 587-7697
 URL:   www.cs.utk.edu/~cates


On Thu, 21 Dec 2000, Luis Ibanez wrote:

> 
> Hi,
> 
> I would like to propose to add a Draft directory for
> Code in the repository, may be something like
> 
>               Insight/Code/Draft
> 
> That will allow us to share code that is in gestation,
> not ready to be in the Common directory yet,
> but for which the input of the group is important.
> 
> Our current strategy is to send poorly typed pseudo
> code in mails, or pieces of code as attachments...
> which after two iterations of replies became like
> trying to do by hand what cvs already do nicely.
> 
> This directory could be out of the building process
> to avoid breaking the nightly builds.
> 
> In this way, code that is just evolving from a rough
> design could be in "public display" to be criticized
> and eventually improved, avoiding the friction caused
> by checkins that are perceived as "sudden".
> 
> Risky modifications of classes that are already in the 
> Common directory could be tried in the Draft too. So
> we could make tentative experiments (again in public)
> without breaking other people's projects.
> 
> 
> Thanks
> 
> 
> Luis
> 
> _______________________________________________
> Insight-developers mailing list
> Insight-developers@public.kitware.com
> http://public.kitware.com/mailman/listinfo/insight-developers
>