Re: [dbutils] 2_0 branch discussion

2020-01-08 Thread Bill Speirs
Everything is as up-to-date as I can tell... just submitted a few merges: https://gitbox.apache.org/repos/asf?p=commons-dbutils.git;a=commit;h=31deec7a232bacb1204c86788939afaac101b0ef Bill- On Sun, Jan 5, 2020 at 1:12 PM Carl Hall wrote: > Thanks for merging that in. Since 2.0 RC1 was cut, ther

Re: [dbutils] 2_0 branch discussion

2020-01-05 Thread Carl Hall
Thanks for merging that in. Since 2.0 RC1 was cut, there have been a few releases on the 1.x line. Is 2_0 up to date with everything? > On Dec 30, 2019, at 4:35 PM, William Speirs wrote: > > I just merged the code from my fork ( > https://github.com/wspeirs/sop4j-dbutils/ >

Re: [dbutils] 2_0 branch discussion

2019-12-30 Thread William Speirs
Gary, I appreciate the sentiment of not wanting to make a major change, but if you look at the commit history and the emails from 2013 you'll realize this last commit is actually fairly small. The only reason this wasn't done in 2013 was that the release process didn't seem to want to work for me,

Re: [dbutils] 2_0 branch discussion

2019-12-30 Thread Gary Gregory
I think we should look at the current code base we have in master and work in new features and bug fixes one PR at a time. Trying some big bang port from some now 'foreign' code base is likely to not get reviewed if it comes in one giant PR. Gary On Mon, Dec 30, 2019 at 5:17 PM Carl Hall wrote:

Re: [dbutils] 2_0 branch discussion

2019-12-30 Thread William Speirs
I just merged the code from my fork ( https://github.com/wspeirs/sop4j-dbutils/) into the commons-dbutils 2_0 branch ( https://gitbox.apache.org/repos/asf?p=commons-dbutils.git;a=commit;h=180c0990b1f0da4d0039904b68cc6b57f00558e5 ). The code builds, and all the tests pass... that's as far as I went

[dbutils] 2_0 branch discussion

2019-12-30 Thread Carl Hall
There was a 2_0 branch started several years ago[1]. That release was abandoned, the code wasn’t merged into master, and a fork was spurred outside of Apache[2]. I’d like to rectify this and work to a release. The code was moved to a different package in both repos, so merging isn’t straightfor