Re: [Sablevm-developer] suggestion: sablevm developer doc

[Prof. E. M. G. <eti...@uq...>]

On Tue, Mar 18, 2003 at 09:28:08AM -0500, Chris Pickett wrote:
>...  There is no maintenance of the branch ... 

That's the problem.  CVS's technical weaknesses dictate that branches
should be short lived.  Except for vendor branches, you can't really
think of maintaining *parallel* stable, experimental, and "private"
developer branches, where changes are merged from any of these to any
other.  You can imagine fixing a bug in stable and wanting to merge
the fix in experimental, *and* the reverse.  CVS is simply not
appropriate for such development model.

I know, you are suggesting to use some other's project development
model (Mozilla).  My reply is to say, we should in the short term
stick to the simplest model (single trunk) to avoid being bitten by
the shortcomings of our support tool (CVS).  I have got money from
NSERC to buy a server to host our development.  Once we have this
server, we can install on it whatever tool we think is more
appropriate.  My quick reading of the subversion home page convinced
me that it would be a far more appropriate tool than CVS, allowing us
to use the Mozilla Development model or change it easily if we find it
is not an appropriate model, without being locked out of interesting
models because of the underlying tool.

I do not plan to buy the server before the Summer, as I do not have
time to shop for it and install it before then.  It also gives us the
time to determine our needs.

Etienne


-- 
Etienne M. Gagnon, Ph.D.             http://www.info.uqam.ca/~egagnon/
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/