[RESULT][VOTE] Release Commons Text 1.3 based on RC1

This [VOTE] passes with the following +1 votes: Gary Gregory, Oliver Heger, Pascal Schumacher, and myself. I will go ahead and perform the promotion mechanics (tomorrow morning…I’ve got a bit of a bug too). And, many thanks for the validations. Cheers, -Rob > On Mar 16, 2018, at 11:35 AM,

Re: [VOTE] Release Commons Text 1.3 based on RC1

Here’s my +1. > On Mar 16, 2018, at 11:35 AM, Rob Tompkins wrote: > > Hello all, > > This is a [VOTE] for releasing Apache Commons Text 1.3 (from RC1). > > Tag name: > commons-text-1.3-RC1 (signature can be checked from git using 'git tag > -v') > > Tag URL: > >

Re: [ANNOUNCE] Commons Parent 45 released.

No problem, pardon having to roll a new release. > On Mar 20, 2018, at 12:00 PM, Gary Gregory wrote: > > Thanks Rob! > > Gary > > On Thu, Mar 15, 2018 at 12:58 PM, Rob Tompkins wrote: > >> [This announcement is only going to the dev list.] >> >>

Re: [DISCUSS] new component for timing?

I would be happy to revive sirona @asf but dont think [monitoring] as just a few classes would bring enough value compare to a lambda not worthing any lib/dep in apps - just my opinion indeed. For circuit breaker: geronimo safeguard can be interested in hosting that utility part and drop failsafe

Re: [DISCUSS] new component for timing?

On Tue, 20 Mar 2018 15:27:45 -0700, Otto Fowler wrote: Sirona is gone, it is a closed incubator project. Romain has forked it to his own repo. The code is there; the rationale is the same: some functionality started "here" and got "there". Is anyone interested to get (part of) it back

Re: [DISCUSS] new component for timing?

Sirona is gone, it is a closed incubator project. Romain has forked it to his own repo. On March 20, 2018 at 18:24:06, Gilles (gil...@harfang.homelinux.org) wrote: On Tue, 20 Mar 2018 15:00:41 -0700, Otto Fowler wrote: > If monitoring was started a new, and not re-viving the old > monitoring?

Re: [DISCUSS] new component for timing?

On Tue, 20 Mar 2018 15:00:41 -0700, Otto Fowler wrote: If monitoring was started a new, and not re-viving the old monitoring? Can the feature be contributed to "Sirona"? Otto, are you interested in this? Does it make sense to have "Commons Monitoring" revived based on part/all of "Sirona"?

Re: [VOTE] Release Commons Text 1.3 based on RC1

+1 Am 16.03.2018 um 16:35 schrieb Rob Tompkins: Hello all, This is a [VOTE] for releasing Apache Commons Text 1.3 (from RC1). Tag name: commons-text-1.3-RC1 (signature can be checked from git using 'git tag -v') Tag URL:

Re: [DISCUSS] new component for timing?

Not sure. I'm not familiar with sirona/commons-monitoring. Sirona seems to already have a StopWatch, and looks like there's some users already? No strong opinion here, so happy with either of these. From: Otto Fowler To: Romain Manni-Bucau

Re: [VFS] FILE_OR_FOLDER breaking tests

You need someone from cold storage! ;-) Gary On Tue, Mar 20, 2018 at 3:53 PM, Otto Fowler wrote: > Anybody from VFS-past around? > > > On March 8, 2018 at 23:55:54, Gary Gregory (garydgreg...@gmail.com) wrote: > > On Thu, Mar 8, 2018 at 8:54 AM, Otto Fowler

Re: [DISCUSS] new component for timing?

If monitoring was started a new, and not re-viving the old monitoring? On March 20, 2018 at 17:56:44, Bruno P. Kinoshita ( brunodepau...@yahoo.com.br.invalid) wrote: I think StopWatch and CircuitBreakers could be moved together to the same component. However, a circuit breaker can be

Re: [DISCUSS] new component for timing?

I think StopWatch and CircuitBreakers could be moved together to the same component. However, a circuit breaker can be time-related, or not (e.g. a circuit breaker for memory size). So probably commons-timing could be a good place for StopWatch, but maybe not for circuit-breaker. But I think

Re: [VFS] FILE_OR_FOLDER breaking tests

Anybody from VFS-past around? On March 8, 2018 at 23:55:54, Gary Gregory (garydgreg...@gmail.com) wrote: On Thu, Mar 8, 2018 at 8:54 AM, Otto Fowler wrote: > FILE_OR_FOLDER just doesn’t seem to be supported in the system completely. > Does anyone remember when it came

Re: [DISCUSS] new component for timing?

I would love to get this on track. I apologize if I have made it more confusing than it needs to be, I’m trying to be open to all the suggestions. If we assume that stack watch is worth ‘having’, then the question is where to put it. commons-monitoring / sirota seems to me to be a ‘complete’

Re: [VOTE] Release Commons Text 1.3 based on RC1

Build works fine with Java 1.7 and 1.8. Artifacts and site look good. So +1. Minor nit: The site has a japicmp report which is just an empty page. Oliver Am 16.03.2018 um 16:35 schrieb Rob Tompkins: > Hello all, > > This is a [VOTE] for releasing Apache Commons Text 1.3 (from RC1). > > Tag

Re: [VOTE] Release Commons Text 1.3 based on RC1

Hi, Thank you for preparing this RC. +1 from src zip: ASC, MD5, SHA1 OK. Apache RAT check OK. CLIRR check OK. 'mvn clean verify site' OK Using: Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T12:49:05-07:00) Maven home: C:\Java\apache-maven-3.5.3 Java version:

Re: [VOTE] Release Commons Text 1.3 based on RC1

I've been down with the flu and just coming out of it noticed this VOTE thread. I will review today. I encourage others to do the same. Gary On Fri, Mar 16, 2018 at 9:35 AM, Rob Tompkins wrote: > Hello all, > > This is a [VOTE] for releasing Apache Commons Text 1.3 (from

Re: [ANNOUNCE] Commons Parent 45 released.

Thanks Rob! Gary On Thu, Mar 15, 2018 at 12:58 PM, Rob Tompkins wrote: > [This announcement is only going to the dev list.] > > Hello All, > > Commons Parent 45 has been released. > > The change from release 44 is: > > - Rearranging plugin order in -Prelease,

Re: [report] Draft board report

Our report has been submitted. Gary On Mon, Mar 19, 2018 at 6:53 PM, Gary Gregory wrote: > Thank you for the review Rob. > > Gary > > On Mon, Mar 19, 2018, 14:15 Rob Tompkins wrote: > >> Looks reasonable from a quick read. >> >> -Rob >> >> > On Mar

Re: [Statistics] Port codes from Commons Math

Hello devs, I have updated my draft proposal with @Gilles's suggestions[Draft Proposal V1.1 ] and I think I need some more clarifications on below suggestions > == "Background" section == > >