Re: [DBCP] Release 2.8.0

Sounds good.  I implemented the DBCP changes this weekend but did not finish testing and I had to make some decisions that would be good to talk about.  I will ask about that in another thread.  I think the pool changes are fine though and will meet the need. On 9/21/20 7:55 AM, Gary Gregory w

Re: [DBCP] Release 2.8.0

On Mon, Sep 21, 2020 at 10:55 AM Gary Gregory wrote: > Hi All: > > I need to pick up the fix "Mask out user name and password from > DriverAdapterCPDS.toString()." ASAP, so I plan on creating a release > candidate later today or tonight. > > I can pick up the new DestroyMode work Phil did in Pool

[DBCP] Release 2.8.0

Hi All: I need to pick up the fix "Mask out user name and password from DriverAdapterCPDS.toString()." ASAP, so I plan on creating a release candidate later today or tonight. I can pick up the new DestroyMode work Phil did in Pool for use in DBCP in a subsequent release. Gary

Re: [DBCP] Release 2.4.0

I will probably cut RC1 tonight or tomorrow. Gary On Sat, Jun 9, 2018 at 9:43 AM Gary Gregory wrote: > Hi All: > > I'd like to release DBCP 2.4.0 ASAP. Please review what you feel like > reviewing... > > Gary >

[DBCP] Release 2.4.0

Hi All: I'd like to release DBCP 2.4.0 ASAP. Please review what you feel like reviewing... Gary

Re: [DBCP] Release 2.3.0

I’ll be near my machine. > On May 7, 2018, at 11:25 PM, Gary Gregory wrote: > > I might get to it tomorrow. > > Gary > >> On Mon, May 7, 2018, 19:00 Rob Tompkins wrote: >> >> >> >>> On May 7, 2018, at 2:25 PM, Gary Gregory wrote: >>> >>> Hi All, >>> >>> Unless someone beats me to it (a

Re: [DBCP] Release 2.3.0

I might get to it tomorrow. Gary On Mon, May 7, 2018, 19:00 Rob Tompkins wrote: > > > > On May 7, 2018, at 2:25 PM, Gary Gregory wrote: > > > > Hi All, > > > > Unless someone beats me to it (and you are welcome to step in :-) I plan > on > > creating a release candidate for our Apache Commons

Re: [DBCP] Release 2.3.0

> On May 7, 2018, at 2:25 PM, Gary Gregory wrote: > > Hi All, > > Unless someone beats me to it (and you are welcome to step in :-) I plan on > creating a release candidate for our Apache Commons DBCP component, > hopefully ASAP. I’m curious to see how my directions go in the release creation

[DBCP] Release 2.3.0

Hi All, Unless someone beats me to it (and you are welcome to step in :-) I plan on creating a release candidate for our Apache Commons DBCP component, hopefully ASAP. Gary

Re: [POOL][DBCP] Release plans

For Pool, I'm not exactly sure why we need a Java 6 compatible implementation for the next minor version (2.5). We've had the EOL discussion before, and even Java 7 is at that point. The only reason I'd look at updating DBCP to use Java 8 is to support JDBC 4.2 < https://docs.oracle.com/javase/8/d

Re: [POOL][DBCP] Release plans

2017-03-06 10:06 GMT+01:00 Mark Thomas : > On 05/03/17 18:21, Matt Sicker wrote: > > I'm also thinking we might want to upgrade to Java 7 for pool 2.5 as dbcp > > 2.x has required it from the beginning. I'm not exactly sure if anything > > JDBC changed in Java 8 to warrant an upgrade to Java 8 for

Re: [POOL][DBCP] Release plans

On 05/03/17 18:21, Matt Sicker wrote: > I'm also thinking we might want to upgrade to Java 7 for pool 2.5 as dbcp > 2.x has required it from the beginning. I'm not exactly sure if anything > JDBC changed in Java 8 to warrant an upgrade to Java 8 for dbcp 2.3, but > it's also worth mentioning if nee

Re: [POOL][DBCP] Release plans

I am +1 to making Java 7 the hard minimum for [pool] and [dbcp] on the next minor release. I'd love: - to see (and use) a fresh release of [pool] followed by [dbcp] - update to Java 7 Gary On Sun, Mar 5, 2017 at 10:21 AM, Matt Sicker wrote: > I'm also thinking we might want to upgrade to Java

Re: [POOL][DBCP] Release plans

I'm also thinking we might want to upgrade to Java 7 for pool 2.5 as dbcp 2.x has required it from the beginning. I'm not exactly sure if anything JDBC changed in Java 8 to warrant an upgrade to Java 8 for dbcp 2.3, but it's also worth mentioning if needed. On 5 March 2017 at 11:59, Pascal Schumac

Re: [POOL][DBCP] Release plans

Great new. :) As far as I remember there were various request for DBCP 2.2 (and we would like to update to pool 2.4.3 at work). Thank you very much, Pascal Am 05.03.2017 um 18:30 schrieb Matt Sicker: I've started a lazy vote to migrate Pool to Git. After that, I'd like to take a whack at sta

Re: [POOL][DBCP] Release plans

Great news Matt. Thank you for driving this effort. Gary On Mar 5, 2017 6:30 PM, "Matt Sicker" wrote: > I've started a lazy vote to migrate Pool to Git. After that, I'd like to > take a whack at starting a release candidate for pool 2.4.3. After that, we > can upgrade DBCP to pool 2.4.3 and do

[POOL][DBCP] Release plans

I've started a lazy vote to migrate Pool to Git. After that, I'd like to take a whack at starting a release candidate for pool 2.4.3. After that, we can upgrade DBCP to pool 2.4.3 and do a release of DBCP to 2.2. -- Matt Sicker

RM karma (was: [DBCP] Release 2.2?)

On 27 July 2016 at 17:06, Gary Gregory wrote: > WRT the KEYS file, I'm not sure we can give karma without Matt being an > actual Commons Committer or a PMC member. Is there such a thing as a Commons Committer since we opened SVN/Git to all? I think karma is granted by updating the LDAP uinx grou

Re: [DBCP] Release 2.2?

No attachment, try garydgregory at gmail dot com. Gary On Wed, Jul 27, 2016 at 12:03 PM, Matt Sicker wrote: > Not sure if attachments work here, but here's the generated file. It > should be the same data as in the Logging KEYS file. > > On 27 July 2016 at 11:06, Gary Gregory wrote: > >> WRT t

Re: [DBCP] Release 2.2?

Not sure if attachments work here, but here's the generated file. It should be the same data as in the Logging KEYS file. On 27 July 2016 at 11:06, Gary Gregory wrote: > WRT the KEYS file, I'm not sure we can give karma without Matt being an > actual Commons Committer or a PMC member. > > For Ne

Re: [DBCP] Release 2.2?

WRT the KEYS file, I'm not sure we can give karma without Matt being an actual Commons Committer or a PMC member. For Nexus, I'll have to research. I think we just did this song and dance not long ago... Matt: Please send me the result of: (echo && pgp -kxa ) >> this file. (echo

Re: [DBCP] Release 2.2?

I have granted you the necessary Karma in JIRA. @Gary: I think we need to setup additional karma so that Matt can write to the keys files and can upload to the Nexus staging repo. I don't know which karma is required. Benedikt Matt Sicker schrieb am Di., 26. Juli 2016 um 23:09 Uhr: > Also, I c

Re: [DBCP] Release 2.2?

Also, I can't edit anything in jira, so I can't update fix versions and whatnot. On 26 July 2016 at 16:07, Matt Sicker wrote: > Or just pull it from the last key in > https://www.apache.org/dist/logging/KEYS > > On 26 July 2016 at 15:58, Matt Sicker wrote: > >> I need my gpg key added to the co

Re: [DBCP] Release 2.2?

Or just pull it from the last key in https://www.apache.org/dist/logging/KEYS On 26 July 2016 at 15:58, Matt Sicker wrote: > I need my gpg key added to the commons KEYS file. I don't have permissions > to commit to it. Here's my key data: > > -BEGIN PGP PUBLIC KEY BLOCK- > Version: GnuPG

Re: [DBCP] Release 2.2?

I need my gpg key added to the commons KEYS file. I don't have permissions to commit to it. Here's my key data: -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v2 Comment: GPGTools - https://gpgtools.org mQINBFMvQKsBEAC3/wuVMv4ia132SA1Y/KnuZYkSNDaRH/Ie1WTAX9X0KrWA5fx2 WmzKfaLNyBHU5aI0BjoE9DW3

Re: [DBCP] Release 2.2?

Well, get started and let us know of any issues we have :-) Gary On Tue, Jul 26, 2016 at 11:43 AM, Matt Sicker wrote: > Nope, this would be my first release here. > > On 26 July 2016 at 13:42, Gary Gregory wrote: > > > Hi Matt, > > > > The only thing that transfer into Commons from other proje

Re: [DBCP] Release 2.2?

Nope, this would be my first release here. On 26 July 2016 at 13:42, Gary Gregory wrote: > Hi Matt, > > The only thing that transfer into Commons from other projects is your > ability to commit. > > Have you ever performed a Commons release before? > > Gary > > On Tue, Jul 26, 2016 at 11:14 AM,

Re: [DBCP] Release 2.2?

Hi Matt, The only thing that transfer into Commons from other projects is your ability to commit. Have you ever performed a Commons release before? Gary On Tue, Jul 26, 2016 at 11:14 AM, Matt Sicker wrote: > Not unless it transfers from other projects. > > On 26 July 2016 at 12:44, Benedikt R

Re: [DBCP] Release 2.2?

Also, yes, I'm interested in being the RM for the next dbcp release. I can start it almost any night this week. On 26 July 2016 at 13:14, Matt Sicker wrote: > Not unless it transfers from other projects. > > On 26 July 2016 at 12:44, Benedikt Ritter wrote: > >> Doe

Re: [DBCP] Release 2.2?

Not unless it transfers from other projects. On 26 July 2016 at 12:44, Benedikt Ritter wrote: > Does Matt already have the necessary karma? > > Gary Gregory schrieb am Di., 26. Juli 2016 um > 19:28: > > > It is under "General Information" in the LHS menu of the site: > > https://commons.apache.

Re: [DBCP] Release 2.2?

Does Matt already have the necessary karma? Gary Gregory schrieb am Di., 26. Juli 2016 um 19:28: > It is under "General Information" in the LHS menu of the site: > https://commons.apache.org/releases/index.html > > Gary > > On Tue, Jul 26, 2016 at 9:36 AM, Matt Sicker wrote: > > > I think I'd b

Re: [DBCP] Release 2.2?

It is under "General Information" in the LHS menu of the site: https://commons.apache.org/releases/index.html Gary On Tue, Jul 26, 2016 at 9:36 AM, Matt Sicker wrote: > I think I'd be up to it. Where can I find info about doing releases? I > don't see anything on the commons site or wiki. > > O

Re: [DBCP] Release 2.2?

I think I'd be up to it. Where can I find info about doing releases? I don't see anything on the commons site or wiki. On 26 July 2016 at 10:59, Gary Gregory wrote: > @Matt: Are you still up for it? > > If so, feel free to drop a note on what you think your ETA would be in > https://issues.apach

Re: [DBCP] Release 2.2?

@Matt: Are you still up for it? If so, feel free to drop a note on what you think your ETA would be in https://issues.apache.org/jira/browse/DBCP-446 (just to be nice ;-) Gary On Thu, Jul 21, 2016 at 9:09 AM, Benedikt Ritter wrote: > No, you just need some karma, which we can grant if you' lik

Re: [DBCP] Release 2.2?

No, you just need some karma, which we can grant if you' like to RM. Matt Sicker schrieb am Do., 21. Juli 2016 um 17:58: > Do you have to be a PMC to do the release? > > On 21 July 2016 at 01:41, Benedikt Ritter wrote: > > > Hello Gary, > > > > Gary Gregory schrieb am Do., 21. Juli 2016 um > >

Re: [DBCP] Release 2.2?

Do you have to be a PMC to do the release? On 21 July 2016 at 01:41, Benedikt Ritter wrote: > Hello Gary, > > Gary Gregory schrieb am Do., 21. Juli 2016 um > 05:59 Uhr: > > > Hi All: > > > > Does anyone feel like spinning up a DBCP 2.2 release? > > > > We have a nice little set of changes and t

Re: [DBCP] Release 2.2?

Hello Gary, Gary Gregory schrieb am Do., 21. Juli 2016 um 05:59 Uhr: > Hi All: > > Does anyone feel like spinning up a DBCP 2.2 release? > > We have a nice little set of changes and the previous release was almost a > year ago. > > Phil, are you feeling RM-y? > I think Phil has left commons tog

[DBCP] Release 2.2?

Hi All: Does anyone feel like spinning up a DBCP 2.2 release? We have a nice little set of changes and the previous release was almost a year ago. Phil, are you feeling RM-y? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

Re: [POOL][DBCP] Release plan

On 2/17/14, 7:17 AM, Mark Thomas wrote: > DBCP 2 is finally close to a release. The rough way ahead is: > - Release Pool 2.2 > - Update DBCP to depend on Pool 2.2 > - Add testOnCreate to DBCP to fix DBCP-249 > - Release DBCP 2.0 > > That will leave 5 enhancement requests open for DBCP that are most

RE: [POOL][DBCP] Release plan

Good news and nice plan! Gary Original message From: Mark Thomas Date:02/17/2014 10:17 (GMT-05:00) To: Commons Developers List Subject: [POOL][DBCP] Release plan DBCP 2 is finally close to a release. The rough way ahead is: - Release Pool 2.2 - Update DBCP to depend on

[POOL][DBCP] Release plan

DBCP 2 is finally close to a release. The rough way ahead is: - Release Pool 2.2 - Update DBCP to depend on Pool 2.2 - Add testOnCreate to DBCP to fix DBCP-249 - Release DBCP 2.0 That will leave 5 enhancement requests open for DBCP that are most likely going to be eventually resolved as WONTFIX un

Re: DBCP release

Olivier Lamy wrote: > Hi, > > Done : http://svn.apache.org/viewvc?view=revision&revision=910339 > Should be ok for next sync. > Thanks! Phil > -- > Olivier > > 2010/2/15 Phil Steitz : >> I have been holding the release announcement until the maven >> artifacts got replicated; but replication ne

Re: DBCP release

Hi, Done : http://svn.apache.org/viewvc?view=revision&revision=910339 Should be ok for next sync. -- Olivier 2010/2/15 Phil Steitz : > I have been holding the release announcement until the maven > artifacts got replicated; but replication needs to be set up for > commons-dbcp/commons-dbcp and I

DBCP release

I have been holding the release announcement until the maven artifacts got replicated; but replication needs to be set up for commons-dbcp/commons-dbcp and I am not sure that has yet been done. Does anyone here have karma / access to tell if the replication has been set up for this directory in m2

Re: [DBCP] Release process suggestion

sebb wrote: > On 24/01/2010, Phil Steitz wrote: >> sebb wrote: >> > release-process.txt currently says: >> > >> > 7. Check out DBCP fully - i.e., trunk, branches, tags. >> > >> > 8. From the top level of the checkout, execute >> > svn cp trunk branches/DBCP_1_3_x_BRANCH >> > svn c

Re: [DBCP] Release process suggestion

On 24/01/2010, Phil Steitz wrote: > sebb wrote: > > release-process.txt currently says: > > > > 7. Check out DBCP fully - i.e., trunk, branches, tags. > > > > 8. From the top level of the checkout, execute > > svn cp trunk branches/DBCP_1_3_x_BRANCH > > svn commit -m "Created 1.3.

Re: [DBCP] Release process suggestion

sebb wrote: > release-process.txt currently says: > > 7. Check out DBCP fully - i.e., trunk, branches, tags. > > 8. From the top level of the checkout, execute > svn cp trunk branches/DBCP_1_3_x_BRANCH > svn commit -m "Created 1.3.x compatibility release branch." > (where x is the f

[DBCP] Release process suggestion

release-process.txt currently says: 7. Check out DBCP fully - i.e., trunk, branches, tags. 8. From the top level of the checkout, execute svn cp trunk branches/DBCP_1_3_x_BRANCH svn commit -m "Created 1.3.x compatibility release branch." (where x is the final digit of the new r