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 2010/12/13 18:29:10 UTC

svn commit: r1045245 - /shiro/board/2010-12.txt

Author: lhazlewood
Date: Mon Dec 13 17:29:10 2010
New Revision: 1045245

URL: http://svn.apache.org/viewvc?rev=1045245&view=rev
Log:
Adjustments due to team recommendations.  Minor additional cleanup.

Modified:
    shiro/board/2010-12.txt

Modified: shiro/board/2010-12.txt
URL: http://svn.apache.org/viewvc/shiro/board/2010-12.txt?rev=1045245&r1=1045244&r2=1045245&view=diff
==============================================================================
--- shiro/board/2010-12.txt (original)
+++ shiro/board/2010-12.txt Mon Dec 13 17:29:10 2010
@@ -12,17 +12,22 @@ Releases:
 Community & Project:
  - No new committers or PMC members
 
+ - Continued user participation on the mailing lists.  This last month
+   probably represents the highest user activity with regards to
+   opening Jira issues and providing patches, a healthy sign that our
+   project continues to grow as a new TLP.
+
  - The development team is discussing as to when our next release might
    be, whether it will be before or after the holidays.  It is not
    currently decided if it will be a 1.1.1 point release or a
    1.2 minor release.
 
- - There has been a lot of discussion in the last month as to the best
-   way to support Shiro integration with 3rd-party (ASF compatible)
-   frameworks and libraries - either include the code as
-   'support modules' within Shiro's codebase, or to have the code
+ - There has been a lot of discussion in the last month by both users and
+   developers as to the best way to support Shiro integration with
+   3rd-party (ASF compatible) frameworks and libraries - either include
+   the code as 'support modules' within Shiro's codebase, or to have the code
    reside somewhere else, like a 'shiro-extras' project, similar in concept
-   to the 'WicketStuff' project.
+   to Apache Wicket's 'Wicket Stuff' project.
 
    The difficulty in deciding is based on 1) the likelyhood of the dev
    team supporting an increasing number of integration modules directly at