This is an automated email from the ASF dual-hosted git repository. slawrence pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/incubator-daffodil-site.git
commit 049a2e60bd95703ee820a01f8908b593110f0be0 Author: Michael Beckerle <[email protected]> AuthorDate: Wed Aug 22 13:41:49 2018 -0400 Updates to formatting and content for RC2 --- site/_releases/2.2.0.md | 41 +++++++++++++++++++++-------------------- 1 file changed, 21 insertions(+), 20 deletions(-) diff --git a/site/_releases/2.2.0.md b/site/_releases/2.2.0.md index d6aa308..59fb61c 100644 --- a/site/_releases/2.2.0.md +++ b/site/_releases/2.2.0.md @@ -3,12 +3,12 @@ released: false apache: true title: 2.2.0 -date: 2018-08-16 +date: 2018-08-22 summary: > -artifact-root: "https://dist.apache.org/repos/dist/dev/incubator/daffodil/2.2.0-rc1/"; -checksum-root: "https://dist.apache.org/repos/dist/dev/incubator/daffodil/2.2.0-rc1/"; +artifact-root: "https://dist.apache.org/repos/dist/dev/incubator/daffodil/2.2.0-rc2/"; +checksum-root: "https://dist.apache.org/repos/dist/dev/incubator/daffodil/2.2.0-rc2/"; key-file: "http://www.apache.org/dist/incubator/daffodil/KEYS"; source-dist: @@ -19,7 +19,7 @@ binary-dist: - "apache-daffodil-2.2.0-incubating-bin.zip" - "apache-daffodil-2.2.0.incubating-1.noarch.rpm" -scala-version: 2.11, 2.12 +scala-version: 2.12 --- @@ -27,9 +27,9 @@ Daffodil 2.2.0 is the second release of Daffodil as an Apache incubator project. This release includes numerous bug fixes and DFDL feature additions to support more DFDL schemas. -#### New Features +### New Features -##### Layering +#### Layering A experimental DFDL language feature known as layering has been added to Daffodil. This feature has been discussed for future inclusion in the DFDL standard by the DFDL working group. The syntax of the properties is subject to some change in the future. The layering feature is described at [Data Layering](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=75979671). @@ -41,7 +41,7 @@ The syntax of the properties is subject to some change in the future. The layeri * {% jira 1934 %} Inability to read data following a layer * {% jira 1935 %} Debugger/trace broken with new layering -##### Message Streaming API +#### Message Streaming API Daffodil's parser API has been enhanced to allow parsing of unbounded streams of messages, symmetric with the Daffodil unparser. The API enables calling the ``parse`` method repeatedly on the same data stream so as to parse one data element (typically a message, but could be any DFDL-described element) at a time from the stream. In prior releases, Daffodil had only a parse API that expected data for the parse to consume the entire data stream. @@ -55,7 +55,7 @@ Documentation for this API is in the [SAPI - Scala API](../../docs/2.2.0/scalado * {% jira 1985 %} beforeState in sequences prevents streaming behavior in I/O layer * {% jira 1987 %} Buckets not released with small bucket sizes -##### Scala 2.12 Support and Library Dependencies Updated +#### Scala 2.12 Support and Library Dependencies Updated Daffodil now supports both Scala 2.11 and Scala 2.12. Most testing is now done on Scala 2.12 with only occasional regression checking done on Scala 2.11. Support for Scala 2.11 will eventually be elminated in a future release. @@ -65,7 +65,7 @@ In addition, Daffodil depends on a number of other libraries. These have been up * {% jira 1973 %} Dependencies on old libraries should be updated * {% jira 1430 %} macroLib should not be needed after scala compilation, but seems to be required -##### Zoned Decimal Text Numbers and Packed Decimal Calendars +#### Zoned Decimal Text Numbers and Packed Decimal Calendars Support for the ``dfdl:textNumberRep`` of ``zoned`` has been added along with the related DFDL properties that specify zoned-number format. @@ -80,34 +80,35 @@ Packed Decimal, and IBM 4690 Packed Decimal, respectively are supported. * {% jira 1943 %} Date, Time, DateTime - Binary - binaryCalendarRep='ibm4690Packed' * {% jira 99 %} Date, Time, DateTime - Binary - binaryCalendarRep='binary' -#### Deprecation/Compatability +### Deprecation/Compatability As of 2.2.0, the following changes have been made which affect compatibility with past releases: -**DFDLGeneralFormat.dfdl.xsd changes** +#### DFDLGeneralFormat.dfdl.xsd changes This DFDL schema is used as a starting point by many schemas. Some changes to it can lead to incompatibilities. -* ``dfdl:calendarTimeZone`` - was ``UTC`` now ```` (unknown time zone). This change often results in Infoset data that does not have the UTC time zone suffix ``+00:00`` appended to it unless a time-zone was specified in the parsed data. In prior releases this suffix would have generally been appended, which was surprising, and deemed incorrect by users. + +Property ``dfdl:calendarTimeZone`` - was ``"UTC"`` now ``""`` (empty string, meaning unknown time zone). This change often results in Infoset data that does not have the UTC time zone suffix ``+00:00`` appended to it unless a time-zone was specified in the parsed data. In prior releases this suffix would have generally been appended, which was surprising, and deemed incorrect by users. * {% jira 1929 %} Parse of date results in date+time-zone specifier - should be just date. * {% jira 1930 %} DFDLGeneralFormat defines calendarTimeZone as UTC - should define as "" -* ``dfdl:occursCountKind`` - was ``parsed`` now ``implicit``. With ``implicit`` the number of element occurrences that will be parsed ends when ``maxOccurs`` is reached. This is generally desirable, especially for optional elements (``minOccurs="0``, ``maxOccurs="1``) where users found it unintuitive that such an element could end up as an array of more than one occurrance. In prior releases the ``dfdl:occursCountKind`` was ``parsed``, which instructs Daffodil to continue parsing as many [...] +Property ``dfdl:occursCountKind`` - was ``parsed`` now ``implicit``. With ``implicit`` the number of element occurrences that will be parsed ends when ``maxOccurs`` is reached. This is generally desirable, especially for optional elements (``minOccurs="0``, ``maxOccurs="1``) where users found it unintuitive that such an element could end up as an array of more than one occurrance. In prior releases the ``dfdl:occursCountKind`` was ``parsed``, which instructs Daffodil to continue parsing [...] * {% jira 1948 %} DFDLGeneralFormat has dfdl:occursCountKind 'parsed'. Should be 'implicit' -* ``dfdl:textNumberRoundingMode`` - was ``roundUnnecessary`` now ``roundHalfEven``. This change should be compatible, and was necessary due to an update of the underlying ICU libraries used by Daffodil. The behavior of that library with respect to rounding modes was fixed, allowing us to change the rounding mode to the more reasonable ``roundHalfEven`` behavior. +Property ``dfdl:textNumberRoundingMode`` - was ``roundUnnecessary`` now ``roundHalfEven``. This change should be compatible, and was necessary due to an update of the underlying ICU libraries used by Daffodil. The behavior of that library with respect to rounding modes was fixed, allowing us to change the rounding mode to the more reasonable ``roundHalfEven`` behavior. -**The ``maxOccursBound`` limit** +#### The ``maxOccursBound`` limit Prior Daffodil releases had a very small limit on the number of repeating occurrences an element could have, 1024, which was not being checked in some cases. It is now checked in all cases; however, with this checking it was discovered that many schemas break on this small limit. The limit was changed to Int.MaxValue (maximum positive value of a 32-bit integer), and must be tuned downward by users who wish to catch situations where there are an excessive number of repeats much larger tha [...] * {% jira 1519 %} occursCount that is greater than maxOccursBounds causes PE/UE rather than SDE -**The ``suppressSchemaDefinitionWarnings`` Tunable** +#### The ``suppressSchemaDefinitionWarnings`` Tunable Some schemas produce large number of schema definition warnings, and it is desirable to tolerate, and suppress these. The name of the tunable is now ``suppressSchemaDefinitionWarnings``. Prior releases used ``suppressWarnings`` which was inconsistent with the API-level access names/symbols for the same concept. @@ -125,9 +126,9 @@ Please see the [Test Data Markup Language (TDML)](../../tdml) page. * {% jira 1961 %} TDML Runner - enhance round-trip to distinguish simple parse-unparse from multi-trip cases * {% jira 1947 %} TDMLRunner - incorrect error on left-over data: TDMLException: Left over data. Consumed 48 bit(s) with 0 bit(s) remaining. -#### Additional Changes +### Additional Changes -##### Infrastructure +#### Infrastructure * {% jira 1962 %} TravisCI builds fail with error 137 out of memory * {% jira 1938 %} RPM/tar/zips contain jars with different hashes @@ -137,7 +138,7 @@ Please see the [Test Data Markup Language (TDML)](../../tdml) page. * {% jira 1982 %} Update Eclipse Paths for new library versions. * {% jira 1925 %} Remove testWSPStar.dfdl.xsd and json5.dfdl.xsd -##### Bugs Fixed +#### Bugs Fixed * {% jira 1923 %} Excel export CSV escaping - can't be handled with standard block escape * {% jira 1984 %} Separator prefix of terminator - not getting longest match @@ -152,7 +153,7 @@ Please see the [Test Data Markup Language (TDML)](../../tdml) page. * {% jira 1969 %} Exception on unparse of string with explicit length and truncateSpecifiedLengthString="yes" * {% jira 1970 %} Exception instead of error message - expression variable on wrong level -##### Other Miscellaneous +#### Other Miscellaneous * {% jira 1918 %} Update JSON schema in tests to use Boolean type * {% jira 1960 %} RepUnboundedParser incorrectly handling points of uncertainty
