I'm amendable on an "avalon" cvs containing next-generation material, but we don't have any next-generation material yet. I think that the next-gen stuff could/should be developed in avalon-sandbox cvs as it makes quite clear what the status of that material is.
When we are ready to start a beta cycle of some kind on sandbox material a new cvs might be a good idea. Until then, I think it is confusing to have this repo, especially as it will/should be empty. Hence I vote -1 for creating it right now. regards, - Leo On Wed, 2002-12-04 at 10:49, Nicola Ken Barozzi wrote: > I propose we have a new "avalon" CVS repository where to develop the new > Avalon5 system. Things will be discussed and committed only when decided > upon, and still eventually changed when again decided upon. > > This will make us do a clear cut with previous development methods, and > clearly indicate that it's a new effort and that the old will be > nevertheless maintained. > > +1 for a new "avalon" CVS repository > > Alternatively it can be called avalon5, avalonV, aValon, avalon-5, > avalon-ng... the important thing is that it's there. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
