Thanks for adding that version. I’ll work on marking tickets that are in this
release.
There have been a few API additions, requiring Java 1.7 instead of 1.6, and the
addition of a new annotation. It feels like enough to go with 1.8 rather than
1.7.1, but I’m open to stronger opinions.
> On J
If you guys can’t sort it out by tomorrow evening, I can roll
1.8.
-Rob
> On Jan 4, 2020, at 6:43 PM, Gary Gregory wrote:
>
> I added 1.8 but the it could be changed to 1.7.1 if no new API is added.
>
> Gary
>
>> On Sat, Jan 4, 2020, 18:40 Carl Hall wrote:
>>
>> I don’t seem to have the ri
I added 1.8 but the it could be changed to 1.7.1 if no new API is added.
Gary
On Sat, Jan 4, 2020, 18:40 Carl Hall wrote:
> I don’t seem to have the right permissions to create a release in Jira for
> DbUtils[1]. Could someone grant me those permissions, or create a 1.8
> release, please? Than
I don’t seem to have the right permissions to create a release in Jira for
DbUtils[1]. Could someone grant me those permissions, or create a 1.8 release,
please? Thanks!
https://jira.apache.org/jira/projects/DBUTILS?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=no-f
Just don't delete any tags...
Gary
On Mon, Dec 30, 2019 at 9:37 AM William Speirs wrote:
> 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 suppor
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 aft
Solid point, Gary, and it removes the collision with 2.0. win-win. :) I’ll
revert that change, and proceed with a 1.8 version for release consideration.
> On Dec 30, 2019, at 6:44 AM, Gary Gregory wrote:
>
> If the only breaking change is a change to field access level, let's revert
> that kee
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 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
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 o
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
10 matches
Mail list logo
