If the only breaking change is a change to field access level, let's revert that keep binary compatibility IMO.
Gary On Mon, Dec 30, 2019 at 1:43 AM Carl Hall <thecarlh...@apache.org> wrote: > Hi all, > > It’s been another couple of years since DbUtils had a release[1], 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[2][3]. Should I jump to 3.0 or > replace the 2.0 RC artifacts? > > Thanks, > Carl > > 1 http://markmail.org/message/7nyhqkuw6cccqf7l < > http://markmail.org/message/7nyhqkuw6cccqf7l> > 2 > https://gitbox.apache.org/repos/asf?p=commons-dbutils.git;a=commit;h=83d65e39ce5ac4ad11f9cfc1294386936b0b2de2 > < > https://gitbox.apache.org/repos/asf?p=commons-dbutils.git;a=commit;h=83d65e39ce5ac4ad11f9cfc1294386936b0b2de2 > > > 3 > https://gitbox.apache.org/repos/asf?p=commons-dbutils.git;a=log;h=refs/tags/DBUTILS_2_0_RC1 > < > https://gitbox.apache.org/repos/asf?p=commons-dbutils.git;a=log;h=refs/tags/DBUTILS_2_0_RC1 > > > >
