jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Schumacher <felix.schumac...@internetallee.de>
Subject Re: [VOTE] Release JMeter 5.2 RC4
Date Sun, 27 Oct 2019 08:28:17 GMT


Am 27. Oktober 2019 08:36:44 MEZ schrieb Philippe Mouawad <pmouawad@apache.org>:
>Hello,
>Could somebody check that Bug 63723 is fixed.

I couldn't reproduce the failure when it was reported. So I don't think I will be able to
reproduce it now. 

Felix 

>
>I checked on my side and found it was.
>My test case was to add a different and significant startup delay for
>thread group of each agent so that the first one ends before the second
>starts.
>
>
>But reporter says it’s not without providing anything useful.
>
>Thanks
>Regards
>
>On Saturday, October 26, 2019, Felix Schumacher <
>felix.schumacher@internetallee.de> wrote:
>
>>
>> Am 26.10.19 um 10:59 schrieb Milamber:
>> >
>> > Ok to start the RC5 today, or anyone need to add some changes?
>>
>> With Vladimir's last changes, the sha512 checksums are generated
>> correctly (in my tests).
>>
>> I have added a few links to gradle.md in the docs and removed a bit
>of
>> misplaced spaces.
>>
>> From my side you can start RC5.
>>
>> Felix
>>
>> >
>> >
>> >
>> >
>> > On 25/10/2019 13:39, Philippe Mouawad wrote:
>> >> Hello,
>> >>
>> >> On french google group, a problem with documentation has been
>reported
>> >>
>> >> Following property logic has been changed, I’ll update doc this
>evening
>> >> unless someone wants to do it before me:
>> >>
>> >> proxy.number.requests Add numeric *prefix* to Sampler
>names.defaults to:
>> >> true
>> >>
>> >> Thanks
>> >> proxy.number.requests Add numeric *prefix* to Sampler
>names.defaults to:
>> >> true
>> >>
>> >>
>> >> On Friday, October 25, 2019, sebb <sebbaz@gmail.com> wrote:
>> >>
>> >>> On Thu, 24 Oct 2019 at 23:20, Vladimir Sitnikov
>> >>> <sitnikov.vladimir@gmail.com> wrote:
>> >>>> Milamber>This vote for RC4 not passed with 2 x -1 (veto) from
>PMC
>> >>>> member.
>> >>>>
>> >>>> As per the ASF policy, releases may not be vetoed.
>> >>> Agreed, the -1 is not a veto in the case of a release; i.e. a
>single
>> >>> -1 does not automatically cancel the release.
>> >>> However -1 votes do count towards the result, and may cause the
>vote to
>> >>> fail.
>> >>>
>> >>> Also the release manager (RM) is at liberty to cancel a vote even
>if
>> >>> there are sufficient +1 votes for it to pass.
>> >>> This can happen if a problem is detected which the RM considers
>serious
>> >>> enough.
>> >>> It's not necessary for existing votes to be changed in order to
>> >>> cancel the
>> >>> vote.
>> >>>
>> >>>>> https://www.apache.org/foundation/voting.html#ReleaseVotes
>> >>>>> Releases **may not** be vetoed
>> >>>> Vladimir
>> >>
>> >
>>

Mime
View raw message