You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Leo Simons <le...@apache.org> on 2002/12/04 13:13:24 UTC
Re: [VOTE] Creation of an "avalon" CVS repository for new Avalon5
codebase (Re: How to move forward?)
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: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] Creation of an "avalon" CVS repository for new Avalon5
codebase (Re: How to move forward?)
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Leo Simons wrote:
> 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.
I understand your point, and it's sensible and has good reasoning.
But IMHO we can also use the new avalon CVS instead of the sandbox dir
*exactly* with the same purpose, and have the history already there and
start from the initial commits. To make it clear we can put a WARNING
file in the main dir and in the docs there. Using the sandbox can also
confuse, since material in there can be or can also not be put in the
main repo, while here we are effectively creating the new repo. Tomcat 5
development is done in the new repo, not in a sandbox or the new one.
Just IMHO that is.
> 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.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] Creation of an "avalon" CVS repository for new Avalon5 codebase (Re: How to move forward?)
Posted by Peter Donald <pe...@realityforge.org>.
-1 for same reasons as below.
On Wed, 4 Dec 2002 23:13, Leo Simons wrote:
> 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.
--
Cheers,
Peter Donald
Einstein argued that there must be simplified explanations of nature, because
God is not capricious or arbitrary. No such faith comforts the software
engineer.
- Fred Brooks, Jr.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] Creation of an "avalon" CVS repository for new Avalon5 codebase (Re: How to move forward?)
Posted by Peter Donald <pe...@realityforge.org>.
-1 for same reasons as below.
On Wed, 4 Dec 2002 23:13, Leo Simons wrote:
> 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.
--
Cheers,
Peter Donald
Einstein argued that there must be simplified explanations of nature, because
God is not capricious or arbitrary. No such faith comforts the software
engineer.
- Fred Brooks, Jr.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] Creation of an "avalon" CVS repository for new Avalon5 codebase (Re: How to move forward?)
Posted by Peter Donald <pe...@realityforge.org>.
-1 for same reasons as below.
On Wed, 4 Dec 2002 23:13, Leo Simons wrote:
> 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.
--
Cheers,
Peter Donald
Einstein argued that there must be simplified explanations of nature, because
God is not capricious or arbitrary. No such faith comforts the software
engineer.
- Fred Brooks, Jr.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] Creation of an "avalon" CVS repository for new Avalon5
codebase (Re: How to move forward?)
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Leo Simons wrote:
> 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.
I understand your point, and it's sensible and has good reasoning.
But IMHO we can also use the new avalon CVS instead of the sandbox dir
*exactly* with the same purpose, and have the history already there and
start from the initial commits. To make it clear we can put a WARNING
file in the main dir and in the docs there. Using the sandbox can also
confuse, since material in there can be or can also not be put in the
main repo, while here we are effectively creating the new repo. Tomcat 5
development is done in the new repo, not in a sandbox or the new one.
Just IMHO that is.
> 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.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] Creation of an "avalon" CVS repository for new Avalon5
codebase (Re: How to move forward?)
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Leo Simons wrote:
> 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.
I understand your point, and it's sensible and has good reasoning.
But IMHO we can also use the new avalon CVS instead of the sandbox dir
*exactly* with the same purpose, and have the history already there and
start from the initial commits. To make it clear we can put a WARNING
file in the main dir and in the docs there. Using the sandbox can also
confuse, since material in there can be or can also not be put in the
main repo, while here we are effectively creating the new repo. Tomcat 5
development is done in the new repo, not in a sandbox or the new one.
Just IMHO that is.
> 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.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>