This is an automated email from the ASF dual-hosted git repository.

aharui pushed a commit to branch release/0.9.2
in repository https://gitbox.apache.org/repos/asf/royale-asjs.git

commit 1e0e876189ec928b8e21abab999080cb2a2e2543
Author: Alex Harui <[email protected]>
AuthorDate: Mon Mar 12 20:14:04 2018 -0700

    keep fixing release notes handling.  Top-level is still plain text
---
 ApproveRoyale.xml        | 16 ++++++++--------
 releasemgr/RELEASE_NOTES | 11 +++++++++++
 2 files changed, 19 insertions(+), 8 deletions(-)

diff --git a/ApproveRoyale.xml b/ApproveRoyale.xml
index 08532ba..396f859 100644
--- a/ApproveRoyale.xml
+++ b/ApproveRoyale.xml
@@ -352,7 +352,7 @@
             reportFile="${src.rat.report}">
             <fileset dir="${basedir}/${package.url.name}">
                 <exclude name="README.md"/>
-                <exclude name="RELEASE_NOTES.md"/>
+                <exclude name="**/RELEASE_NOTES.md"/>
                 <exclude name="**/README.md"/>
                 <exclude name="LICENSE.bin"/>
                 <exclude name="LICENSE.base"/>
@@ -416,7 +416,7 @@
             reportFile="${bin.rat.report}">
             <fileset dir="${basedir}/${bin.package.url.name}">
                 <exclude name="README.md"/>
-                <exclude name="RELEASE_NOTES.md"/>
+                <exclude name="**/RELEASE_NOTES.md"/>
                 <exclude name="**/README.md"/>
                 <exclude name="LICENSE.bin"/>
                 <exclude name="LICENSE.base"/>
@@ -652,10 +652,10 @@
                    </not>
                        </condition>
         </fail>
-        <fail message="RELEASE_NOTES.md not in package">
+        <fail message="RELEASE_NOTES not in package">
                        <condition>
                                <not>
-                                       <available 
file="${basedir}/${package.url.name}/RELEASE_NOTES.md" />
+                                       <available 
file="${basedir}/${package.url.name}/RELEASE_NOTES" />
                                </not>
                        </condition>
         </fail>
@@ -682,10 +682,10 @@
         defaultvalue="y"
         addproperty="readme.ok"/>
                <antcall target="display-text" >
-            <param name="file" 
value="${basedir}/${package.url.name}/RELEASE_NOTES.md" />
+            <param name="file" 
value="${basedir}/${package.url.name}/RELEASE_NOTES" />
         </antcall>
                <input
-                       message="Check the RELEASE_NOTES.md for copyright 
years, spelling, grammar, accuracy. Is it ok?"
+                       message="Check the RELEASE_NOTES for copyright years, 
spelling, grammar, accuracy. Is it ok?"
             validargs="y,n"
         defaultvalue="y"
         addproperty="releasenotes.ok"/>
@@ -1045,7 +1045,7 @@ OS: ${os.name} ${os.arch} ${os.version}
 Source kit signatures match: y
 Source kit builds: y
 README is ok: ${readme.ok}
-RELEASE_NOTES.md is ok: ${releasenotes.ok}
+RELEASE_NOTES is ok: ${releasenotes.ok}
 NOTICE is ok: ${notice.ok}
 LICENSE is ok: ${license.ok}
 No unapproved licenses or archives: ${rat.license.ok}
@@ -1073,7 +1073,7 @@ OS: ${os.name} ${os.arch} ${os.version}
 Source kit signatures match: y
 Source kit builds: y
 README is ok: ${readme.ok}
-RELEASE_NOTES.md is ok: ${releasenotes.ok}
+RELEASE_NOTES is ok: ${releasenotes.ok}
 NOTICE is ok: ${notice.ok}
 LICENSE is ok: ${license.ok}
 No unapproved licenses or archives: ${rat.license.ok}
diff --git a/releasemgr/RELEASE_NOTES b/releasemgr/RELEASE_NOTES
index c56e4c2..268e6dd 100644
--- a/releasemgr/RELEASE_NOTES
+++ b/releasemgr/RELEASE_NOTES
@@ -1,3 +1,14 @@
+Apache Royale 0.9.2
+===================
+
+This release contains:
+
+- Virtual item renderer management for fixed row height vertical lists.
+- Improved Theme support. The compiler will copy all resources in "assets" 
+  folder to target.
+- JSON deserialization to ActionScript objects
+- JSON2ASVO utility to generate ActionScript Value Objects from a JSON result
+
 Apache Royale 0.9.1
 ===================
 

-- 
To stop receiving notification emails like this one, please contact
[email protected].

Reply via email to