RE: [VOTE] Release CRYPTO 1.0.0 based on RC1

>> It would be neat if we could get Jenkins to do that for us! Thank you for your suggestion, I will do some investigation about it. -Original Message- From: Gary Gregory [mailto:garydgreg...@gmail.com] Sent: Wednesday, August 03, 2016 10:22 AM To: Commons Developers List

Re: [VOTE] Release CRYPTO 1.0.0 based on RC1

On Tue, Aug 2, 2016 at 7:19 PM, Sun, Dapeng wrote: > Hi Gary, > > >>Where are the instructions to actually build the same jar contained in > the bin-zip with ALL of the native libraries for Windows, Mac, and Linux? > Thank you for your comments. I will add a wiki for it. >

RE: [VOTE] Release CRYPTO 1.0.0 based on RC1

Hi Gary, >>Where are the instructions to actually build the same jar contained in the >>bin-zip with ALL of the native libraries for Windows, Mac, and Linux? Thank you for your comments. I will add a wiki for it. According the previous discussion, I copied the native binary files complied by

RE: [MATH]: Current state of project?

On Tue, 2 Aug 2016 09:35:43 -0700, Dennis E. Hamilton wrote: There are a number of dangling [VOTE] threads that seem to devolve into inconclusive discussion. Nevertheless, it would be useful for the creator of those votes to resolve them with [RESULT][VOTE] messages that account for any actual

Re: [VOTE] Release DBCP 2.2 based on RC1

Fine with me. You should send a [VOTE][RESULT] thread. I'm happy to change my vote to -1 to if you want to make it official. Gary On Tue, Aug 2, 2016 at 12:52 PM, Matt Sicker wrote: > I'd like to cancel this release and start RC2 if there are no objections. > > On 2 August

Re: [VOTE] Release DBCP 2.2 based on RC1

I'd like to cancel this release and start RC2 if there are no objections. On 2 August 2016 at 14:41, Matt Sicker wrote: > Minor issue in the changelog: DBCP-452 has an "unknown" type due to a typo > in the word "type" in the xml. I'll fix that with DBCP-454. > > On 2 August

Re: [VOTE] Release DBCP 2.2 based on RC1

Minor issue in the changelog: DBCP-452 has an "unknown" type due to a typo in the word "type" in the xml. I'll fix that with DBCP-454. On 2 August 2016 at 13:48, Matt Sicker wrote: > Oh cool, I found an earlier issue I duplicated. >

Re: [configuration] Checkstyle settings

Am 02.08.2016 um 08:54 schrieb Dennis Kieselhorst: > Am 01.08.2016 um 21:31 schrieb Oliver Heger: >> Am 31.07.2016 um 22:24 schrieb Matt Sicker: >>> Fixing all the checkstyle errors first is kind of a prerequisite to >>> enabling it by default. >>> >>> On 31 July 2016 at 15:10, Charles Honton

Re: [VOTE] Release DBCP 2.2 based on RC1

Oh cool, I found an earlier issue I duplicated. https://issues.apache.org/jira/browse/DBCP-454 On 2 August 2016 at 13:01, Matt Sicker wrote: > I'm working on a fix for DBCP-465 (the fix is done, the test is still > being worked on as I've never used pax-exam before). With that

Re: [VOTE] Release DBCP 2.2 based on RC1

I'm working on a fix for DBCP-465 (the fix is done, the test is still being worked on as I've never used pax-exam before). With that in mind, I'm voting -1 (non-binding) for this release candidate. On 2 August 2016 at 11:51, Matt Sicker wrote: > I've created

Re: [VOTE] Release DBCP 2.2 based on RC1

I've created . Can we fix this and make a new release candidate, or is this release going to pass the vote technically? On 1 August 2016 at 17:53, Matt Sicker wrote: > It very well could be. The basic OSGi tests in log4j could

RE: [MATH]: Current state of project?

There are a number of dangling [VOTE] threads that seem to devolve into inconclusive discussion. Nevertheless, it would be useful for the creator of those votes to resolve them with [RESULT][VOTE] messages that account for any actual votes cast and where there were no votes. In ASF parlance,

Re: [MATH]: Current state of project?

On Tue, Aug 2, 2016 at 11:55 AM, Rob Tompkins wrote: > Hey Artem, > > I agree. I've decided to make some contributions in commons more generally > to gain report as to become a committer. Until I can do that, I'm guessing > that it'll just be Gilles accepting pill requests. >

Re: [MATH]: Current state of project?

> On Aug 1, 2016, at 10:58 PM, Artem Barger wrote: > > Hello everyone, > > It's been a while since there was a lot of hot discussion regarding the > future of the CM project, however I do not think that clear agreement was > reached. The reason I'm wondering is because I'd

Re: [VOTE] Release CRYPTO 1.0.0 based on RC1

I know the VOTE is closed but I wanted to note that I was able to build with : Apache Maven 3.3.9 Maven home: /usr/share/maven Java version: 1.8.0_91, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-8-openjdk-i386/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux",

Re: [RESULT] [VOTE] Release CRYPTO 1.0.0 based on RC1

Hey, contratulations. I cannot remember the last time a RC1 passed the vote ;-) Sun, Dapeng wrote: > This vote passed[1].(Three binding +1, three non-binding +1, no +0 or -1). > > The following people voted on release CRYPTO 1.0.0: > > Benedikt Ritter+1 (binding) > Jörg Schaible

Re: [VOTE] Release Configuration 2.1 based on RC2

Hi Gary! > We have a mini-mess here: > > - checkstyle's check is called from the build and it fails. > - Did it ever work? > - Did it work and then the code degraded between the last release and this > code base? The 2.0 checkstyle is clean: >

[RESULT] [VOTE] Release CRYPTO 1.0.0 based on RC1

This vote passed[1].(Three binding +1, three non-binding +1, no +0 or -1). The following people voted on release CRYPTO 1.0.0: Benedikt Ritter+1 (binding) Jörg Schaible +1(binding) Hendrik Saly +1 Marcelo Vanzin+1 Jochen Wiedmann +1(binding) Ke Xianda +1 Thank all

Re: [configuration] Checkstyle settings

Am 01.08.2016 um 21:31 schrieb Oliver Heger: > Am 31.07.2016 um 22:24 schrieb Matt Sicker: >> Fixing all the checkstyle errors first is kind of a prerequisite to >> enabling it by default. >> >> On 31 July 2016 at 15:10, Charles Honton wrote: >> >>> Why wouldn’t we want build to