Hello,
Due of the API backward issue with Ubik plugin, I cancel the vote and
start the next RC3 asap.
Milamber
On 01/04/2017 16:23, Milamber wrote:
Hello,
The second release candidate for JMeter 3.2 (r1789808) has been
prepared, and your votes are solicited.
This release brings new
On 4 April 2017 at 10:49, sebb wrote:
> On 4 April 2017 at 09:52, sebb wrote:
>> On 3 April 2017 at 21:52, Philippe Mouawad
>> wrote:
>>> Thanks Milamber !
>>> Maybe we should run this tool (
>>>
On 4 April 2017 at 09:52, sebb wrote:
> On 3 April 2017 at 21:52, Philippe Mouawad wrote:
>> Thanks Milamber !
>> Maybe we should run this tool (
>> https://github.com/lvc/japi-compliance-checker) on JMeter 3.2 RC2 vs 3.1 to
>> double check there are
On 3 April 2017 at 21:52, Philippe Mouawad wrote:
> Thanks Milamber !
> Maybe we should run this tool (
> https://github.com/lvc/japi-compliance-checker) on JMeter 3.2 RC2 vs 3.1 to
> double check there are no other similar non identified issues.
That would have to be
Thanks Milamber !
Maybe we should run this tool (
https://github.com/lvc/japi-compliance-checker) on JMeter 3.2 RC2 vs 3.1 to
double check there are no other similar non identified issues.
Regards
On Mon, Apr 3, 2017 at 9:20 PM, Milamber wrote:
> Hello,
>
> I will cancel
Hello,
I will cancel the RC2 vote and start a RC3 next Wednesday or Friday
(after the re-introduction of the removed API. cc Philippe).
Please continue your test about RC2 to find a lot of bugs before the RC3 ;-)
Milamber
On 03/04/2017 10:45, Antonio Gomes Rodrigues wrote:
Hi,
Like
Hi,
Like Philippe
[X] I do not support this release
In my opinion, we need to deprecate this API in 3.2 release and remove it
in 3.3
Antonio
2017-04-03 7:40 GMT+02:00 Philippe Mouawad :
> Hello,
> Thanks Milamber for your work on RM for this.
>
> Due to issue
Hello,
Thanks Milamber for your work on RM for this.
Due to issue reported my vote is:
[X] I do not support this release
I can fix issue if ok for you to commit in trunk.
Regards
On Sunday, April 2, 2017, Philippe Mouawad
wrote:
> Hello,
> I am to blame for
Hello,
I am to blame for this issue, sorry !
http://svn.apache.org/viewvc?rev=1783666=rev
Regards
On Sun, Apr 2, 2017 at 3:08 PM, UBIK LOAD PACK Support <
supp...@ubikloadpack.com> wrote:
> Hello,
> Note this is annoying as fixing it would mean that our plugin would only
> support 3.2.
> We
Hello,
Note this is annoying as fixing it would mean that our plugin would only
support 3.2.
We usually try to support N and N-1 versions to allow for migration.
And this was usually the policy with JMeter releases.
Hope you can take this into account.
Regards
On Sun, Apr 2, 2017 at 3:03 PM,
Hello,
First thanks a lot for all the team for the great work on Apache JMeter and
thanks to RM !
Now for this release, it appears HeaderManager API has been modified in a
breaking and undocumented way:
This method:
-
Am 01.04.2017 um 18:23 schrieb Milamber:
Hello,
The second release candidate for JMeter 3.2 (r1789808) has been
prepared, and your votes are solicited.
This release brings new features and fixes bugs.
Please, test this release candidate (with load tests and/or functional
tests) using Java 8
+1
Andrey Pokhilko
On 01.04.2017 19:23, Milamber wrote:
> Hello,
>
> The second release candidate for JMeter 3.2 (r1789808) has been
> prepared, and your votes are solicited.
>
> This release brings new features and fixes bugs.
>
> Please, test this release candidate (with load tests and/or
+1
-Original Message-
From: Milamber [mailto:milam...@apache.org]
Sent: Saturday, April 1, 2017 11:23 AM
To: JMeter Dev List <dev@jmeter.apache.org>
Subject: [VOTE] Release JMeter 3.2 RC2
Hello,
The second release candidate for JMeter 3.2 (r1789808) has been prepared, and
your
Hello,
The second release candidate for JMeter 3.2 (r1789808) has been
prepared, and your votes are solicited.
This release brings new features and fixes bugs.
Please, test this release candidate (with load tests and/or functional
tests) using Java 8 on Linux/Windows/Mac OS, especially on
15 matches
Mail list logo