I found the list of open and in-progress issues sorted by priority
(https://issues.apache.org/jira/issues/?jql=project%20%3D%20DAFFODIL%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC).
I
I would also like to see the updates to SAX merged--there's some
important API conformance and performance fixes that are worth getting
in. There's an open pull request (PR #478) that I think is close to
being ready to be merged.
Of the open critical issues, I think DAFFODIL-2399 might be worth
bl
> I believe we need to do a release very soon regardless of these 96 issues
I would like DAFFODIL- 2482 to get into it;
https://github.com/apache/daffodil/pull/520
Will increase priority on wrapping this up.
On Mon, Apr 12, 2021 at 12:43 PM Beckerle, Mike <
mbecke...@owlcyberdefense.com> wrote
I'd like to discuss our need to create a new release of Daffodil, which would
be 3.1.0.
We have added enough new functionality certainly to justify a release. There
are important features already complete, there is the new Runtime2 backend, etc.
The challenge is that we have 96 JIRA tickets spe
> the code is here https://github.com/jw3/example-daffodil-debug
There is now a complete console based example for Zio that demonstrates
controlling the debug flow while distributing the current state to three
"displays".
1. infoset at current step
2. diff of infoset against previous step
3. bit p
