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.
Despite a feeling by some that a decision has been taken on this, current votes stand in a tie like this:

o Creation of an "avalon" CVS repository for new Avalon5
codebase
+1: nicolaken, mcconnell
+0: cziegeler
-0: proyal
-1: leosimons, leif


Anyone else wants to say his?

--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>



Reply via email to