svn commit: r561776 - /wicket/common/docs/reports/2007-august.txt

[al...@apache.org]

Author: almaw
Date: Wed Aug  1 05:16:05 2007
New Revision: 561776

URL: http://svn.apache.org/viewvc?view=rev&rev=561776
Log:
Some minor fixes

Modified:
    wicket/common/docs/reports/2007-august.txt

Modified: wicket/common/docs/reports/2007-august.txt
URL: http://svn.apache.org/viewvc/wicket/common/docs/reports/2007-august.txt?view=diff&rev=561776&r1=561775&r2=561776
==============================================================================
--- wicket/common/docs/reports/2007-august.txt (original)
+++ wicket/common/docs/reports/2007-august.txt Wed Aug  1 05:16:05 2007
@@ -9,17 +9,16 @@
 
 Community
 
-The migration of the user list is going well and users are migrating without problems. User involvement is good, both when it comes to answering questions and in willingness in submitting detailed bug reports and patches.
+The migration of the user mailing list from SourceForge is going well and users are migrating without problems. User involvement is good, both when it comes to answering questions and in willingness to submit detailed bug reports and patches.
 
 No new committers this month
 
 Migration to TLP
 
-Wicket has been established as TLP. Many thanx to Infrastructure for their help.
+Wicket has been established as a top level project. Many thanks to Apache's Infrastructure team for their help in migrating us across from incubation.
 
-The user mailing list has been created and we have started telling our users on the SourceForge mailing list to migrate to the new list. There will be a very short transition period were both lists will be open for posts, to help existing discussions to only span one list.
+The new user mailing list has been created and we have started telling our users on the SourceForge mailing list to migrate to the new list. There will be a short transition period where both lists are active, and we have set up headers, etc. to actively encourage our users to migrate.
 
 Software
 
-We are working one fixing issues for the third beta of 1.3. This is taking longer than expected because issues keep arising, though at a slower pace than earlier.
-
+We are working on fixing issues for the third beta of 1.3. This is taking longer than expected because issues keep arising, though at a slower pace than earlier. This will position us well for a full release candidate.