+1 on this plan Scala 2.13 has long term support from the Scala Center (see https://www.scala-lang.org/development/), so Daffodil 3.11.0 will be usable but also supportable, though only if necessary for critical vulnerabilities, well into the future.
On Tue, May 13, 2025 at 8:49 AM Steve Lawrence <slawre...@apache.org> wrote: > +1 > > Just for additional clairification, this means there are no plans to > maintain > the Daffodil 3.x series, so Daffodil 3.11.0 will be last release using > Scala > 2.x. We could reevaluate this if critical vulnerabilities are found, but > we do > not plan any Daffodil 3.x maintenance releases. > > > On 2025-05-12 12:28 PM, Adams, Joshua wrote: > > All, > > > > It's been roughly 4 months since the release of Daffodil 3.10.0 and a > significant amount of work has been done in transitioning the code base > from Scala 2.12 to newer versions of Scala. Our current plan is to do a > 3.11.0 release of Apache Daffodil in the upcoming weeks that will target > Scala 2.13. Daffodil 3.11.0 will also include a few relatively small bug > fixes and the usual dependency updates, but the vast majority of the > changes are for Scala 2.13 support. > > > > After Daffodil 3.11.0 is released, our plan for 4.0.0 is to move to > Scala 3, targeting the most recent LTS version which is currently Scala > 3.3.6. Daffodil 4.0.0 will also include a fairly significant overhaul of > our API as well as some bug fixes that may break some existing schemas that > rely on current incorrect behavior (see DAFFODIL-1971 - > https://issues.apache.org/jira/projects/DAFFODIL/issues/DAFFODIL-1971). > > > > As always we are open to and appreciate input from the Daffodil > community. If anyone has any questions, thoughts, or concerns please feel > free to share. > > > > I'm volunteering to be the release manager 3.11.0. > > > > Josh Adams > > > > > >
