RE: ICU library version - was: IBM DFDL is upgrading ICU level

[Interrante, John A (GE Research, US)]

The fix to ICU's Java code changes only a single line and adds a new test case. 
 But that single line was causing 400 test cases in IBM DFDL to fail because 
it'd made ICU's Java code behave differently than ICU's C code (ouch).  The 
difference seems to be mostly rounding of real numbers, e.g., df.format(1235.5) 
with pattern "##00" was producing "1236.0" instead of the expected "1236".  
Ideally the PR will be merged, ICU Java will produce "1236" like ICU C does, 
and IBM's 400 test cases will pass again even though some of Daffodil's test 
cases may or may not even notice this difference in behavior (it'll depend on 
whether any test were using this kind of pattern on real numbers).

-Original Message-
From: Beckerle, Mike  
Sent: Wednesday, May 19, 2021 8:54 AM
To: dev@daffodil.apache.org
Subject: EXT: ICU library version - was: IBM DFDL is upgrading ICU level

DFDL implementors at IBM have noticed some issues with the ICU library worth 
noting.
There is an ICU pull request to fix, targeted at ICU version 70.1.


From: 
Subject: IBM DFDL is upgrading ICU level

Hi Mike

We are moving up the level of ICU that IBM DFDL is built with, as it is still 
on 51 which is out-of-support. We are trying 68.x.
In the process we found several of our regression tests failed due to behaviour 
changes in lax decimal/calendar processing.
If you recall we deliberately changed the DFDL 1.0 spec to make lax 
implementation-dependent/defined (I forget which).
We've analysed the differences and most are to do with bug fixes or other 
changes that are acceptable or benign or we don't think any of our customer 
will hit.
However, we got 400 failures in our Java version which didn't appear in our C 
version.
This looks to be have been caused by a regression somewhere, we think back in 
62 - see https://unicode-org.atlassian.net/browse/ICU-20425.
ICU have accepted there is a problem and the fix is in PR 
https://github.com/unicode-org/icu/pull/1726 which is targeted at 70.1.
Letting you know as moving to 70.1 and higher might therefore cause a Daffodil 
behaviour change.

Regards

Steve Hanson

IBM Hybrid Integration, Hursley, UK
Architect, IBM 
DFDL
Co-Chair, OGF DFDL Working Group

ICU library version - was: IBM DFDL is upgrading ICU level

[Beckerle, Mike]

DFDL implementors at IBM have noticed some issues with the ICU library worth 
noting.
There is an ICU pull request to fix, targeted at ICU version 70.1.


From: 
Subject: IBM DFDL is upgrading ICU level

Hi Mike

We are moving up the level of ICU that IBM DFDL is built with, as it is still 
on 51 which is out-of-support. We are trying 68.x.
In the process we found several of our regression tests failed due to behaviour 
changes in lax decimal/calendar processing.
If you recall we deliberately changed the DFDL 1.0 spec to make lax 
implementation-dependent/defined (I forget which).
We've analysed the differences and most are to do with bug fixes or other 
changes that are acceptable or benign or we don't think any of our customer 
will hit.
However, we got 400 failures in our Java version which didn't appear in our C 
version.
This looks to be have been caused by a regression somewhere, we think back in 
62 - see https://unicode-org.atlassian.net/browse/ICU-20425.
ICU have accepted there is a problem and the fix is in PR 
https://github.com/unicode-org/icu/pull/1726 which is targeted at 70.1.
Letting you know as moving to 70.1 and higher might therefore cause a Daffodil 
behaviour change.

Regards

Steve Hanson

IBM Hybrid Integration, Hursley, UK
Architect, IBM 
DFDL
Co-Chair, OGF DFDL Working Group

Re: 224 legacy Resolved Daffodil JIRA tickets

[Steve Lawrence]

Agreed, +1

Any old tickets that have been resolved but not closed can probably be
assumed to have been correctly fixed. Otherwise someone would have
likely ran into the issue and reopened the ticket.

And if we do discover an issue wasn't fixed, we can also reopen a ticket
or create a new one.

Also, pruning these old tickets will make it easier to stay on top of
resolved ticket verification and maybe make getting involved with
verification for new contributors less intimidating.


On 5/19/21 7:51 AM, Sood, Harinder wrote:
> Agreed
> 
> 
> Sincerely,
>   Harinder Sood |Director (Senior Project Manager)
> 
> hs...@owlcyberdefense.com
> M  240 805 4219
> Work: 410 290-1411 x122
> Connect with us!
> 
> 
> 
> The information contained in this transmission is for the personal and 
> confidential use of the individual or entity to which it is addressed. If the 
> reader is not the intended recipient, you are hereby notified that any 
> review, dissemination, or copying of this communication is strictly 
> prohibited. If you have received this transmission in error, please notify 
> the sender immediately
> 
> 
> -Original Message-
> From: Interrante, John A (GE Research, US)  
> Sent: Wednesday, May 19, 2021 7:46 AM
> To: dev@daffodil.apache.org
> Subject: RE: 224 legacy Resolved Daffodil JIRA tickets
> 
> No one seems to have expressed an opinion, so I think it would be acceptable 
> to close all those resolved tickets over two years old. :)
> 
> John
> 
> From: Thompson, Dave 
> Sent: Tuesday, May 18, 2021 1:12 PM
> To: dev@daffodil.apache.org
> Subject: EXT: 224 legacy Resolved Daffodil JIRA tickets
> 
> All,
> 
> There are currently 224 Daffodil JIRA tickets resolved in previous releases, 
> all but 2 from v2.5.0 (1/2/2020) and earlier.
> 
> I want to check with the group to see if it would be acceptable to close 
> these tickets with "Closed due to no activity."
> 
> Any other suggestions would be appreciated.
> 
> Thanks
> 
> Dave
> 
> 
> Dave Thompson | Senior Engineer, Services 
> [cid:image001.png@01D6EB27.668D0C60][cid:B56B1568CE764B45BDFED4218E40FC7F@namprd15.prod.outlook.com]
> dthomp...@owlcyberdefense.com
> (410) 290-1411 x162
> Connect with us!
> [cid:image007.png@01D6EB27.831BAFD0][cid:0BA4A128A2B66B4DA089690E224FDC76@namprd15.prod.outlook.com][cid:image008.png@01D6EB27.831BAFD0][cid:C85317EB3F4C374DAED9C63921A117CB@namprd15.prod.outlook.com]
> [cid:image006.jpg@01D6EB27.668D0C60][cid:587196D3525EC044850F26DFA35020BD@namprd15.prod.outlook.com]
> 
> The information contained in this transmission is for the personal and 
> confidential use of the individual or entity to which it is addressed. If the 
> reader is not the intended recipient, you are hereby notified that any 
> review, dissemination, or copying of this communication is strictly 
> prohibited. If you have received this transmission in error, please notify 
> the sender immediately
> 
> 
> 

[ANNOUNCE] Apache Daffodil 3.1.0 Released

[Steve Lawrence]

The Apache Daffodil community is pleased to announce the
release of version 3.1.0.

Notable changes in this release include a new code generation backend,
Schematron validation, variable improvements, improved SAX conformance
and performance, and miscellaneous bug fixes/improvements.

Detailed release notes and downloads are available at:

https://daffodil.apache.org/releases/3.1.0/

Apache Daffodil is an open-source implementation of the DFDL
specification that uses DFDL data descriptions to parse fixed format
data into an infoset. This infoset is commonly converted into XML or
JSON to enable the use of well-established XML or JSON technologies
and libraries to consume, inspect, and manipulate fixed format data in
existing solutions. Daffodil is also capable of serializing or
"unparsing" data back to the original data format. The DFDL infoset
can also be converted directly to/from the  data structures carried by
data processing frameworks so as to bypass any XML/JSON overheads.

For more information about Daffodil visit:

https://daffodil.apache.org/

Regards,
The Apache Daffodil Team

RE: 224 legacy Resolved Daffodil JIRA tickets

[Sood, Harinder]

Agreed


Sincerely,
  Harinder Sood |Director (Senior Project Manager)

hs...@owlcyberdefense.com
M  240 805 4219
Work: 410 290-1411 x122
Connect with us!



The information contained in this transmission is for the personal and 
confidential use of the individual or entity to which it is addressed. If the 
reader is not the intended recipient, you are hereby notified that any review, 
dissemination, or copying of this communication is strictly prohibited. If you 
have received this transmission in error, please notify the sender immediately


-Original Message-
From: Interrante, John A (GE Research, US)  
Sent: Wednesday, May 19, 2021 7:46 AM
To: dev@daffodil.apache.org
Subject: RE: 224 legacy Resolved Daffodil JIRA tickets

No one seems to have expressed an opinion, so I think it would be acceptable to 
close all those resolved tickets over two years old. :)

John

From: Thompson, Dave 
Sent: Tuesday, May 18, 2021 1:12 PM
To: dev@daffodil.apache.org
Subject: EXT: 224 legacy Resolved Daffodil JIRA tickets

All,

There are currently 224 Daffodil JIRA tickets resolved in previous releases, 
all but 2 from v2.5.0 (1/2/2020) and earlier.

I want to check with the group to see if it would be acceptable to close these 
tickets with "Closed due to no activity."

Any other suggestions would be appreciated.

Thanks

Dave


Dave Thompson | Senior Engineer, Services 
[cid:image001.png@01D6EB27.668D0C60][cid:B56B1568CE764B45BDFED4218E40FC7F@namprd15.prod.outlook.com]
dthomp...@owlcyberdefense.com
(410) 290-1411 x162
Connect with us!
[cid:image007.png@01D6EB27.831BAFD0][cid:0BA4A128A2B66B4DA089690E224FDC76@namprd15.prod.outlook.com][cid:image008.png@01D6EB27.831BAFD0][cid:C85317EB3F4C374DAED9C63921A117CB@namprd15.prod.outlook.com]
[cid:image006.jpg@01D6EB27.668D0C60][cid:587196D3525EC044850F26DFA35020BD@namprd15.prod.outlook.com]

The information contained in this transmission is for the personal and 
confidential use of the individual or entity to which it is addressed. If the 
reader is not the intended recipient, you are hereby notified that any review, 
dissemination, or copying of this communication is strictly prohibited. If you 
have received this transmission in error, please notify the sender immediately

RE: 224 legacy Resolved Daffodil JIRA tickets

[Interrante, John A (GE Research, US)]

No one seems to have expressed an opinion, so I think it would be acceptable to 
close all those resolved tickets over two years old. :)

John

From: Thompson, Dave 
Sent: Tuesday, May 18, 2021 1:12 PM
To: dev@daffodil.apache.org
Subject: EXT: 224 legacy Resolved Daffodil JIRA tickets

All,

There are currently 224 Daffodil JIRA tickets resolved in previous releases, 
all but 2 from v2.5.0 (1/2/2020) and earlier.

I want to check with the group to see if it would be acceptable to close these 
tickets with "Closed due to no activity."

Any other suggestions would be appreciated.

Thanks

Dave


Dave Thompson | Senior Engineer, Services
[cid:image001.png@01D6EB27.668D0C60][cid:B56B1568CE764B45BDFED4218E40FC7F@namprd15.prod.outlook.com]
dthomp...@owlcyberdefense.com
(410) 290-1411 x162
Connect with us!
[cid:image007.png@01D6EB27.831BAFD0][cid:0BA4A128A2B66B4DA089690E224FDC76@namprd15.prod.outlook.com][cid:image008.png@01D6EB27.831BAFD0][cid:C85317EB3F4C374DAED9C63921A117CB@namprd15.prod.outlook.com]
[cid:image006.jpg@01D6EB27.668D0C60][cid:587196D3525EC044850F26DFA35020BD@namprd15.prod.outlook.com]

The information contained in this transmission is for the personal and 
confidential use of the individual or entity to which it is addressed. If the 
reader is not the intended recipient, you are hereby notified that any review, 
dissemination, or copying of this communication is strictly prohibited. If you 
have received this transmission in error, please notify the sender immediately