I think 3.5.1 is the right number, as that is consistent with our odd-bug fix, even-features convention on the 2nd component of the version number.
So 3.6.0 should be for the next addition of true new features. On Wed, Oct 18, 2023 at 9:20 AM Steve Lawrence <slawre...@apache.org> wrote: > 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? >