You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by rg...@apache.org on 2013/03/27 00:04:59 UTC

svn commit: r1461366 - in /wookie/trunk: NEW_AND_NOTEWORTHY RELEASE_NOTES UPGRADING

Author: rgardler
Date: Tue Mar 26 23:04:57 2013
New Revision: 1461366

URL: http://svn.apache.org/r1461366
Log:
prepare documentation for 0.14 release

Modified:
    wookie/trunk/NEW_AND_NOTEWORTHY
    wookie/trunk/RELEASE_NOTES
    wookie/trunk/UPGRADING

Modified: wookie/trunk/NEW_AND_NOTEWORTHY
URL: http://svn.apache.org/viewvc/wookie/trunk/NEW_AND_NOTEWORTHY?rev=1461366&r1=1461365&r2=1461366&view=diff
==============================================================================
--- wookie/trunk/NEW_AND_NOTEWORTHY (original)
+++ wookie/trunk/NEW_AND_NOTEWORTHY Tue Mar 26 23:04:57 2013
@@ -1 +1,22 @@
-# New and Noteworthy: 0.14
\ No newline at end of file
+# New and Noteworthy: 0.14
+
+## Stability in production
+
+This is primarily a bug fix release that improves on stability in
+production environments where widgets are often updated in situ.
+
+## Improved Localization
+
+A number of bug fixes to the localization feature ensures Wookie is
+useful in a broader set of geographic regions.
+
+## Multiple Parent templates
+
+Improvements to the widget templating system allow templates to have
+multiple parents which each of which can add specfic enhancements.
+
+## Settings Template
+
+A new settings template allows a configuration file defined settings
+page to be added to any existing widget built from templates with
+minimal effort.
\ No newline at end of file

Modified: wookie/trunk/RELEASE_NOTES
URL: http://svn.apache.org/viewvc/wookie/trunk/RELEASE_NOTES?rev=1461366&r1=1461365&r2=1461366&view=diff
==============================================================================
--- wookie/trunk/RELEASE_NOTES (original)
+++ wookie/trunk/RELEASE_NOTES Tue Mar 26 23:04:57 2013
@@ -1,30 +1,82 @@
-Apache Wookie Release Notes
-===========================
-See https://issues.apache.org/jira/browse/WOOKIE-* (where * is the number of the issue below)
-
-For more detailed information on significant changes, see NEW_AND_NOTEWORTHY
-
-Version 0.14
-============
-
-
-Known Issues
-============
-
-    * WOOKIE-222 - There is a known issue when using Tomcat 7.* with Wookie. Sometimes when a widget is actually 
-    loaded, a browser alert box sometimes appears informing the user of a "Session Error". 
-
-    This is caused by the DWR library used by Wookie for Comet-based widgets handling HTTP-only cookies incorrectly; 
-    Tomcat 7 uses HTTP-only cookies as the default setting to prevent cross-site scripting (XSS) attacks.
-
-    A workaround is to add the following to the WEB-INF/web.xml file
-
-    <init-param>
-        <param-name>crossDomainSessionSecurity</param-name>
-        <param-value>false</param-value>
-    </init-param>
-
-    Note that XSS prevention will still be in place in Tomcat 7; this just disables the additional mechanism
-    implemented in DWR that conflicts with it.
- 
+Apache Wookie Release Notes
+===========================
+See https://issues.apache.org/jira/browse/WOOKIE-* (where * is the number of the issue below)
+
+For more detailed information on significant changes, see NEW_AND_NOTEWORTHY
+
+Version 0.14
+============
+
+BUGS FIXED
+==========
+
+WOOKIE-403  
+ProxyServlet doesn't work well on chunked data 
+ 
+WOOKIE-406  
+Widget redeploying fails on Windows
+ 
+WOOKIE-404  
+Server crashed after long wait, while reloading widget
+ 
+WOOKIE-405  
+Widget localization does not work 
+ 
+WOOKIE-387  
+deploying flatpack to another wookie results in an error
+ 
+WOOKIE-382  
+Flatpack function returns wrong widget package
+ 
+WOOKIE-402  
+Package files are overwritten by updates 
+
+WOOKIE-399  
+Twitter widget: public timeline no longer works 
+ 
+WOOKIE-290  
+Widget templates not allowing content to be overwritten properly
+ 
+WOOKIE-386  
+HTML Hex-encoded unicode entities are incorrectly encoded in start files
+ 
+WOOKIE-44  
+Default widget returns js "error" when loaded into a browser 
+ 
+IMPROVEMENTS
+============
+
+WOOKIE-360  
+Process all start files, not just specified locales 
+ 
+WOOKIE-397  
+Improvements to assetPlayer Template
+
+WOOKIE-366  
+Update to the Walkthrough template and test widget 
+
+NEW FEATURES
+============
+
+None
+
+Known Issues
+============
+
+    * WOOKIE-222 - There is a known issue when using Tomcat 7.* with Wookie. Sometimes when a widget is actually 
+    loaded, a browser alert box sometimes appears informing the user of a "Session Error". 
+
+    This is caused by the DWR library used by Wookie for Comet-based widgets handling HTTP-only cookies incorrectly; 
+    Tomcat 7 uses HTTP-only cookies as the default setting to prevent cross-site scripting (XSS) attacks.
+
+    A workaround is to add the following to the WEB-INF/web.xml file
+
+    <init-param>
+        <param-name>crossDomainSessionSecurity</param-name>
+        <param-value>false</param-value>
+    </init-param>
+
+    Note that XSS prevention will still be in place in Tomcat 7; this just disables the additional mechanism
+    implemented in DWR that conflicts with it.
+ 
     This is an issue for DWR 2.* with Tomcat 7.* (or earlier versions of Tomcat where useHttpOnly="true" is set.)
\ No newline at end of file

Modified: wookie/trunk/UPGRADING
URL: http://svn.apache.org/viewvc/wookie/trunk/UPGRADING?rev=1461366&r1=1461365&r2=1461366&view=diff
==============================================================================
--- wookie/trunk/UPGRADING (original)
+++ wookie/trunk/UPGRADING Tue Mar 26 23:04:57 2013
@@ -1,6 +1,10 @@
 This document details any special actions that need to be taken when upgrading Wookie from a previous version. For
 general information on new features and improvements, see NEW_AND_NOTEWORTHY.
 
+FROM 0.13.1 TO 0.14.0
+=====================
+No major changes to the core or database schema. 
+
 FROM 0.11.0 TO 0.13.1 (Version 0.12.0 was not released)
 =====================
 No major changes to the core or database schema. The W3CParser module has been updated so it is possible