Re: [VOTE][RC6] Release Commons RNG 1.0 (reminder)

2016-12-10 Thread Artem Barger
I am voting +1 Отправлено с iPhone > 11 дек. 2016 г., в 8:11, Gilles написал(а): > >> On Wed, 07 Dec 2016 00:22:30 +0100, Gilles wrote: >> Hi. >> >> This is a [VOTE] for releasing Apache Commons RNG 1.0 (from RC6). >> >> >> Tag name: >> RNG_1_0_RC6 (signature

Re: [VOTE][RC6] Release Commons RNG 1.0 (reminder)

2016-12-10 Thread Gilles
On Wed, 07 Dec 2016 00:22:30 +0100, Gilles wrote: Hi. This is a [VOTE] for releasing Apache Commons RNG 1.0 (from RC6). Tag name: RNG_1_0_RC6 (signature can be checked from git using 'git tag -v') Tag URL:

Re: (DBUTILS-131) Speedup query calls without parameters

2016-12-10 Thread Matt Sicker
The ticket mentioned Sybase, so I'm going to assume that. Also, I think you meant to comment on the ticket, not the email. On 10 December 2016 at 16:36, Bernd Eckenfels wrote: > Hello, > What database system/driver did you test? Did you test repeating > statements or

Re: (DBUTILS-131) Speedup query calls without parameters

2016-12-10 Thread Bernd Eckenfels
Hello, What database system/driver did you test? Did you test repeating statements or not. Because some drivers optimize statement caches only for prepared statements. This also means it should be configurable. Gruss Bernd -- http://bernd.eckenfels.net On Sat, Dec 10, 2016 at 10:34 PM

Re: [ALL] Why is the component's web site part of the release vote?

2016-12-10 Thread sebb
On 10 December 2016 at 10:54, Stian Soiland-Reyes wrote: > That sounds like not a problem at all as RAT passes on the RC. > Just regenerate the site after releasing. (We have to verify download page > manually anyway). > > (Perhaps building the site from the RC's tar-ball rather

Re: [ALL] Why is the component's web site part of the release vote?

2016-12-10 Thread Stian Soiland-Reyes
That sounds like not a problem at all as RAT passes on the RC. Just regenerate the site after releasing. (We have to verify download page manually anyway). (Perhaps building the site from the RC's tar-ball rather than the "dirty" mvn tree post release is safer) I think it would only block a