nicolaken 2002/12/04 10:27:24
Modified: . STATUS.txt
Log:
Indented.
Revision Changes Path
1.4 +28 -21 jakarta-avalon/STATUS.txt
Index: STATUS.txt
===================================================================
RCS file: /home/cvs/jakarta-avalon/STATUS.txt,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- STATUS.txt 4 Dec 2002 18:22:58 -0000 1.3
+++ STATUS.txt 4 Dec 2002 18:27:24 -0000 1.4
@@ -3,28 +3,32 @@
Background:
- Apache Avalon is a project started at java.apache.org. It later became an
- Apache Jakarta subproject. It has recently been declared a new top-level
- project with its own PMC.
+ Apache Avalon is a project started at java.apache.org.
+ It later became an Apache Jakarta subproject.
+ It has recently been declared a new top-level project with
+ its own PMC.
See the bottom of this file for the official resolution/
charter-as-it-stands. See the project website for other information.
Release:
- o none scheduled ATM; still defining new container plan and how to best
keep
- development of current code go ahead without impacting negatively on
- the new work.
+ o none scheduled ATM; still defining new container plan and
+ how to best keep development of current code go ahead
+ without impacting negatively on the new work.
- o past releases available from
http://jakarta.apache.org/builds/jakarta-avalon/
+ o past releases available from
+ http://jakarta.apache.org/builds/jakarta-avalon/
- o nightlies available from
http://cvs.apache.org/builds/jakarta-avalon/nightly/
+ o nightlies available from
+ http://cvs.apache.org/builds/jakarta-avalon/nightly/
Resolved Issues:
- o previously released software needs to be supported, including but not
- limited to the avalon framework, avalon excalibur and avalon phoenix
+ o previously released software needs to be supported,
+ including but not limited to the avalon framework, avalon
+ excalibur and avalon phoenix
o existing avalon users must be supported, including but not limited
to the XML Cocoon and Jakarta JAMES communities
@@ -36,7 +40,8 @@
all non-released code. It has its own site to make less confusion
with released products.
- o Use a unified avalon-dev mailing list (and avalon-user remains
separate)
+ o Use a unified avalon-dev mailing list
+ (and avalon-user remains separate)
Pending issues:
@@ -47,15 +52,17 @@
o deciding on moving or not moving to avalon.apache.org
- o discussing and writing medium-to-long term roadmap regarding containers
- and possible avalon framework extension based on consensus development
-
- o discussing and writing short-to-medium term roadmap regarding unused
and/
- or unmaintained and/or alpha-stage software packages in current CVSes
-
- o discussing and writing short-to-medium term roadmap regarding possible
- relocation of software packages that could have a better home at
another
- avalon project
+ o discussing and writing medium-to-long term roadmap
+ regarding containers and possible avalon framework extension
+ based on consensus development
+
+ o discussing and writing short-to-medium term roadmap regarding
+ unused and/or unmaintained and/or alpha-stage software
+ packages in current CVSes
+
+ o discussing and writing short-to-medium term roadmap
+ regarding possible relocation of software packages that
+ could have a better home at another avalon project
o wrap up discussion on licensing headers in sourcefiles
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
