nicolaken 2002/12/05 00:05:44
Modified: . STATUS.txt
Log:
Resolved about sandbox code marking.
The proposal does not pass.
Revision Changes Path
1.8 +7 -13 jakarta-avalon/STATUS.txt
Index: STATUS.txt
===================================================================
RCS file: /home/cvs/jakarta-avalon/STATUS.txt,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- STATUS.txt 5 Dec 2002 08:03:44 -0000 1.7
+++ STATUS.txt 5 Dec 2002 08:05:44 -0000 1.8
@@ -43,6 +43,12 @@
o Use a unified avalon-dev mailing list
(and avalon-user remains separate)
+ o To mark sandbox code clearly as being sandbox code,
+ we do not require that components in this place are
+ put in the package org.apache.avalon.sandbox.X; they
+ will use the same package names they will use if/when
+ they are graduated in main CVS.
+
Pending issues:
@@ -88,18 +94,6 @@
-0: proyal
-1: leosimons, leif
- o Proposed by Peter Donald:
- Mark sandbox code clearly as being sandbox code.
- To do this we could require that components in this place are
- put in the package org.apache.avalon.sandbox.X
- This will make it very clear to users what the status of code
- is and thus they won't be misled into thinking that it is
- anything it is not.
- +1: proyal, leosimons
- +0:
- -0:
- -1: mcconnell, leosutic, nicolaken, bloritsch, stefano, leif
-
o Proposed by Peter Donald:
One of the problems that has plagued Avalon is the result
of one-man codebases. I propose we remove almost all of these
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
