Personally, I think the release process for every new release could include updating outdated dependencies to newer versions. We have an open bug "Update to latest dependencies" that could be added to the list of bugs marked for 3.0.0:
DAFFODIL-2269 Update to latest dependencies The best sbt equivalent of "mvn versions:display-dependency-updates" and "mvn versions:display-plugin-updates" appears to be https://github.com/rtimush/sbt-updates which was last updated 2 days ago. A blogger also did a good job explaining how Maven, Ivy, and Coursier differ in handling version ordering and version ranges (https://eed3si9n.com/dependency-resolver-semantics). Once we have an updated list of newer versions, someone has to read each upgraded dependency's release notes or changelog to make sure the newer versions are upwardly compatible or worth the upgrade cost. I may be able to take on that bug once I finish helping one of my work teams make a software release and make more progress on my runtime2 pull request's requested changes. Someone else is welcome to take that bug too. John -----Original Message----- From: Steve Lawrence <slawre...@apache.org> Sent: Wednesday, October 21, 2020 9:42 AM To: dev@daffodil.apache.org Subject: EXT: [DICSUSS] Daffodil 3.0.0 It's been a few months since a release, and I think we are near a point where many of the major features planned for this release are merged or close to it. I'd like to start a discussion to determine what remaining issues should be resolved for the release. Below is the list of bugs currently marked for 3.0.0, which all have someone assigned, and all look like they'll be merged in the coming days. Is anyone aware of any other bugs that you think should be added to this list? Also, any volunteers for 3.0.0 release manager? We've gone through a couple of iterations of the new release process documented at the following link, so it should be relatively painless. # Release Workflow: https://cwiki.apache.org/confluence/display/DAFFODIL/Release+Workflow # 3.0.0 Unresolved Issues: DAFFODIL-2377 Abort instead of diagnostic message DAFFODIL-2408 iCalendar schema + data causes Daffodil to abort DAFFODIL-1272 Unparsing - Optimizing pruning of infoset elements that aren't needed by any future expressions DAFFODIL-2383 Implement SAX API DAFFODIL-2337 Update unsupported features and errata page for 2.6.0 and 2.7.0 DAFFODIL-2399 Error diagnostics output even though there is an infoset DAFFODIL-2363 pattern facet can't use  notation. Makes validating NUL very hard. DAFFODIL-2382 JAPI withExternalVariables requires Scala Map
