+1 for a release "real soon now".

As for what we need to fix before that release, there are a number of
outstanding tickets related to the new warning mechanism about ignored
properties.

We really shouldn't roll forward with these unresolved issues.

Is there a switch or small change we can make to disable this
mechanism (or have it off by default) without rolling back the actual
commit(s)?

I do expect these ignored property warnings will help users isolate
schema bugs, some of which are undetected in current schemas. It's an
important feature for us to have.  But the open tickets indicate it
isn't correct nor complete yet.

There is so much other good stuff on the main branch that I think it
is well worth creating 3.10.0 without the ignored property warnings
feature.

See:

https://issues.apache.org/jira/browse/DAFFODIL-2875  - shows that
shared groups and type definitions in the schema compiler defeat the
current algorithm for detecting unused properties.

https://issues.apache.org/jira/browse/DAFFODIL-2964 - we get too many
warnings from the regression suite - likely indicates we're getting
false warnings? (could be same issue as DAFFODIL-2875, or something
else.)

https://issues.apache.org/jira/browse/DAFFODIL-2798 - ignored property
detector doesn't detect enumeration facet unused properties.

On Fri, Jan 3, 2025 at 10:26 AM Adams, Joshua
<jad...@owlcyberdefense.com> wrote:
>
> All,
>
> It's been roughly 3 months since the release of Daffodil 3.9.0 and a number 
> of bug fixes and some performance improvements have been added in the mean 
> time, so I would like to discuss beginning the release process for Daffodil 
> 3.10.0.  There are a few outstanding PR's that we should be able to get 
> merged next week and then we can hopefully begin the release process on the 
> following Monday (1/13/25) and allow for a release on the 16th if things go 
> smoothly.  Are there any other significant issues or improvements that we 
> want to get included in a 3.10.0 release?
>
> I'm volunteering to be the release manager this go around.
>
> Josh Adams

Reply via email to