Re: [build-plugin] Re-engineering/release streamlining

2017-11-11 Thread Chas Honton
Take a look at how the maven team votes and publishes Chas > On Nov 11, 2017, at 8:26 PM, Matt Benson wrote: > > On Nov 11, 2017 9:32 PM, "Rob Tompkins" wrote: > > > >>> On Nov 11, 2017, at 10:24 PM, Gary Gregory wrote: >>> >>> On Sat, Nov 11, 2017 at 8:19 PM, Rob Tompkins wrote: >>> >>

Re: [build-plugin] Re-engineering/release streamlining

2017-11-11 Thread Matt Benson
On Nov 11, 2017 9:32 PM, "Rob Tompkins" wrote: > On Nov 11, 2017, at 10:24 PM, Gary Gregory wrote: > >> On Sat, Nov 11, 2017 at 8:19 PM, Rob Tompkins wrote: >> >> Hello all, >> >> I was wondering if we might think about a 2.X line in the [build-plugin] >> to better facilitate our release mech

Re: [build-plugin] Re-engineering/release streamlining

2017-11-11 Thread Rob Tompkins
> On Nov 11, 2017, at 10:24 PM, Gary Gregory wrote: > >> On Sat, Nov 11, 2017 at 8:19 PM, Rob Tompkins wrote: >> >> Hello all, >> >> I was wondering if we might think about a 2.X line in the [build-plugin] >> to better facilitate our release mechanics so that we don’t have to jump >> through

Re: [build-plugin] Re-engineering/release streamlining

2017-11-11 Thread Gary Gregory
On Sat, Nov 11, 2017 at 8:19 PM, Rob Tompkins wrote: > Hello all, > > I was wondering if we might think about a 2.X line in the [build-plugin] > to better facilitate our release mechanics so that we don’t have to jump > through all of these hoops that we do when building a release candidate? > >

[build-plugin] Re-engineering/release streamlining

2017-11-11 Thread Rob Tompkins
Hello all, I was wondering if we might think about a 2.X line in the [build-plugin] to better facilitate our release mechanics so that we don’t have to jump through all of these hoops that we do when building a release candidate? Steps: 1. Move the commons-build-plugin to git. 2. Fully rewrite

Re: [dbcp] update to pool 2.4.3.

2017-11-11 Thread Matt Sicker
The last time I tried to RM a Commons project, I had a lot of blockers. I'm not sure if they were all resolved. Anyways, I may have time to try that out tomorrow. Otherwise, most of this week is taken up by a hackathon going on at work. On 11 November 2017 at 14:57, Gary Gregory wrote: > I was

Re: [dbcp] update to pool 2.4.3.

2017-11-11 Thread Gary Gregory
I was able to build master commons-dbcp based on commons-pool2 master/2.5.0-SNAPSHOT. All tests pass in both builds :-) Do you have time to push out a release commons-pool2 release? A branch for 2.4.4 or master for 2.5.0, either way would be OK with me. Gary On Fri, Nov 10, 2017 at 2:17 PM, Matt

Re: Fwd: [jira] [Resolved] (CONFIGURATION-675) Add .gitignore file

2017-11-11 Thread Oliver Heger
Am 11.11.2017 um 21:22 schrieb Gary Gregory: > I do not think we need a JIRA for this kind of housekeeping... Agreed. However, in this case, the ticket has been created externally, and I just followed the normal workflow to resolve it. Oliver > > Gary > -- Forwarded message --

Fwd: [jira] [Resolved] (CONFIGURATION-675) Add .gitignore file

2017-11-11 Thread Gary Gregory
I do not think we need a JIRA for this kind of housekeeping... Gary -- Forwarded message -- From: Oliver Heger (JIRA) Date: Sat, Nov 11, 2017 at 8:24 AM Subject: [jira] [Resolved] (CONFIGURATION-675) Add .gitignore file To: iss...@commons.apache.org [ https://issues.apache

Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

2017-11-11 Thread Thomas Vandahl
On 06.11.17 21:11, Romain Manni-Bucau wrote: > created > http://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1-RC2/ > (rev 1814438) Thanks, Romain. However, the POM file in this RC tag contains now --8<-- scm:svn:http://svn.apache.org/repos/asf/commons/proper/jcs/tags/co