nicolaken 2003/02/01 02:01:43
Modified: . STATUS.txt
Log:
The questions at the bottom are just sanity checks that we have
remembered all relevant things. They are not to be voted here.
Revision Changes Path
1.28 +0 -8 jakarta-avalon/STATUS.txt
Index: STATUS.txt
===================================================================
RCS file: /home/cvs/jakarta-avalon/STATUS.txt,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- STATUS.txt 1 Feb 2003 09:59:48 -0000 1.27
+++ STATUS.txt 1 Feb 2003 10:01:43 -0000 1.28
@@ -180,39 +180,31 @@
- Should we have a minimum set of requirements before components
are released?
- +0: nicolaken
- If yes to above then which things should be part of minimum
requirements?
documentation: require basic overview and user docs
- +0: nicolaken
uptodate website: require website be updated to latest release
but may still host previous release docs.
- +0: nicolaken
unit tests: (okay so this will never get consensus but ...)
- +0: nicolaken
versioning standard: derived from
http://apr.apache.org/versioning.html
http://jakarta.apache.org/commons/versioning.html
- +0: nicolaken
release process: derived from
http://jakarta.apache.org/commons/releases.html
http://jakarta.apache.org/turbine/maven/development/release-process.html
http://cvs.apache.org/viewcvs.cgi/jakarta-ant/ReleaseInstructions?rev=1.9.2.1&content-type=text/vnd.viewcvs-markup
- +0 nicolaken
deprecation process: (java specific?)
http://jakarta.apache.org/turbine/maven/development/deprecation.html
- +0: nicolaken
CVS/Subversion branching:
http://jakarta.apache.org/turbine/maven/development/branches.html
- +0: nicolaken
Assets:
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
