Yes, I have some C code generator changes that I haven't had time to collect into a PR yet. I would like to get them into this release, so they don't have to wait for the next release.
The deprecation of relative schemaLocation outputs new warnings which I think warrants a minor version bump. A patch version bump implies to me that I can upgrade without needing to change anything in my code. If I see new warnings, however, I'm going to change my code immediately to fix the new warnings (to avoid adding to tech debt), so that means this release isn't just a patch update. I already had to add / to some schemaLocations in some schemas around here after the change went in to fix these warnings, so I'm speaking from experience. John -----Original Message----- From: Steve Lawrence <slawre...@apache.org> Sent: Wednesday, October 18, 2023 9:21 AM To: dev@daffodil.apache.org Subject: EXT: [DISCUSS] Release Apache Daffodil 3.6.0 (or 3.5.1) WARNING: This email originated from outside of GE. Please validate the sender's email address before clicking on links or attachments as they may not be safe. It's been a few months since our last release, so I think it's about time for our next one. If there are no objections, I'd like to start the release process early next week. Does anyone have changes they were hoping to get into this release, or know of any critical issues that should be resolved? I may try to get some last minute performance improvements in, but I don't think it's worth holding up the release. Additionally, it's been suggested that we should only bump the patch version to 3.5.1 instead o releasing as 3.6.0 since the changes have primarily been focused on big fixes. Does anyone have any thought on which version to bump to? Note that there are a few commits labeled as a deprecation or compatibility, including: - Multiple changes related to dflx:repType, including removal of some related functions - Deprecation of relative schemaLocations that resolve absolutely--maintains existing behavior but outputs warnings - Changes to exceptions thrown when usage error occur We have also updated the minor version of some dependencies, including scala-xml (2.1.0 -> 2.2.0) and Saxon-HE (12.2 -> 12.3). Do any of these changes warrant a minor version bump, or should we just bump a patch version?
