It’s been another couple of years since DbUtils had a release, and some good changes are ready to ship. Since the 1.7 release, we’ve had 90+ commit from Commons committers and GitHub PRs. Some features, a threading fix, and lots of attention to builds and quality across all platforms and functionality.
I raise my hand to manage this release. Unless something pops up, I’ll get a vote out to review RC articles in a week or 2. All comments and questions welcome.
There’s one breaking change by reducing access to a 7 yr old deprecated field, so the version should be a major bump. There’s an old RC1 artifact for a 2.0 release that wasn’t completed. Should I jump to 3.0 or replace the 2.0 RC artifacts?
That 2.0 release attempt was mine... Feel free to blow it away, and proceed
with your release as 2.0.
However, most of my changes in there should be working. The changes add
named parameter support, and a fluent API to the library. The only reason
it wasn't released was because I couldn't figure out the release process,
and after much frustration, gave up:
Thanks for reminding me of that, Bill. I have a local branch where I’ve rebased 2_0 onto master, and reworked things where needed. I’ll review that again to see where things stand. It was a lot of work last time, so I’ll plan to go forward without it for now, and try to get a 2.0 release out after the one proposed below. I’ll likely need your help in reviewing the final results. :)