+1 for creating a 4.0.0 release To me the biggest thing needed is not anything to hold up the release, it's documentation on how to evolve a DFDL schema project on github (or similar) and package server (e.g., like Artifactory) in such a way that it can be maintained to work with Daffodil 3.7.0, 3.10.0, 3.11.0, and 4.0.0 (and subsequent) releases simultaneously, easily rebuilt and tested in regression, etc. I pick those because the API (specifically packages) changed after 3.7.0, 3.10.0 is the last of the Scala 2.12 releases, 3.11.0 is Scala 2.13, and 4.0.0 is Scala 3.
There are two scenarios - First is a pure schema - single component. The DFDLSchemas FakeTDL is one such. The second is a complex multi-component schema. The PCAP schema on DFDLSchemas is such. It uses EthernetIP as a component and that has a Daffodil layer extension to compute IPv4 checksums. This should illustrate all the challenges. I think this methodology is going to require use of multiple git branches, since there are clearly code changes required for the layers. I think these use only standard TDML tests however, so ad-hoc test rigs shouldn't muddy the waters. But despite these git branches, much of the schema will be independent of them, and an objective should be to share what can be shared so as not to do too much cross-branch duplication of changes. On Tue, Sep 2, 2025 at 3:03 PM Steve Lawrence <[email protected]> wrote: > Hi all, > > Although Daffodil 3.11.0 was release fairly recently, the current main > branch of > Daffodil has a number of major improvements, including switching to Scala > 3, > dropping official support for Java 8 and 11, a much improved API, and a > number > of important bug fixes. With these major changes complete, I think now > would be > a good time to release Daffodil 4.0.0. > > For reference, here is a page that describes all the breaking changes and > how to > migrate to the new API: > > https://daffodil.apache.org/migration-guides/4.0.0/ > > We should also plan to release the Daffodil SBT plugin 1.5.0 concurrently, > since > it has modifications needed to work with Daffodil 4.0.0. > > There are a dozen or so open pull requests to update dependencies that I > think > we can merge in the coming days in time for 4.0.0. Please let us know if > there > are any other issues you think should be fixed. > > If there are no additional changes or objections, I will volunteer as the > release manager and plan to start the vote on Monday, Sep 8. > > Thanks, > - Steve >
