You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@shiro.apache.org by lh...@apache.org on 2008/10/08 16:24:44 UTC

svn commit: r702890 - /incubator/jsecurity/board/2008-10.txt

Author: lhazlewood
Date: Wed Oct  8 07:24:43 2008
New Revision: 702890

URL: http://svn.apache.org/viewvc?rev=702890&view=rev
Log:
added 2008 October board report

Added:
    incubator/jsecurity/board/2008-10.txt

Added: incubator/jsecurity/board/2008-10.txt
URL: http://svn.apache.org/viewvc/incubator/jsecurity/board/2008-10.txt?rev=702890&view=auto
==============================================================================
--- incubator/jsecurity/board/2008-10.txt (added)
+++ incubator/jsecurity/board/2008-10.txt Wed Oct  8 07:24:43 2008
@@ -0,0 +1,27 @@
+2008-October JSecurity Incubator status report
+
+JSecurity is a powerful and flexible open-source Java security framework
+that cleanly handles authentication, authorization, enterprise session
+management and cryptography.
+
+JSecurity has been incubating since June 2008.
+
+Last month, a new external release was issued (0.9.0-RC2).  After this, a single bug fix has been implemented and
+committed to the external SourceForge SVN repository.  Many other commits have been made, but all were nonfunctional
+and were made to round out the project's JavaDoc.
+
+The JavaDoc is already quite good, but not 100%.  The team has discussed on the development
+list that it would be a good idea to get the JavaDoc completed at 100% before releasing 0.9 final, with 0.9 final being
+the last external release.  After this point, we wanted to inject the code source into the Apache repository as a
+'clean slate' initiative.
+
+The idea is that perhaps 0.9.1 would be an Apache release, allowing that release to focus only on adherence to Apache
+policy and not dependant on code or documentation.  Then all subsequent releases could benefit from the experience of
+this 'first run', continuing to maintain Apache policy.
+
+The JavaDoc is currently being updated intermittently, as the development team has the opportunity to update it in
+their spare time.  It is cerrtainly desireable to finish this effort soon, hopefully no more than a week or two. but
+this time frame is ultimately dependent upon the number of contributors.
+
+The status is being maintained at
+http://svn.apache.org/repos/asf/incubator/jsecurity/STATUS