You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jmeter.apache.org by sebb <se...@gmail.com> on 2013/12/30 02:03:32 UTC
Release 2.10.1 ?
Are we OK to release 2.10.1?
The main reason for doing this is to improve the error handling /
reporting for the keytool utilities. I hope that is now OK.
Are there any other fixes that must to go into the release?
I don't think we should add any new functionality for this release.
It's more important to get the keytool fixes deployed.
Anyone particularly want to be RM?
Re: Release 2.10.1 ?
Posted by sebb <se...@gmail.com>.
On 30 December 2013 09:52, Philippe Mouawad <ph...@gmail.com> wrote:
> On Monday, December 30, 2013, Milamber wrote:
>
>>
>> Le 30/12/2013 02:03, sebb a ecrit :
>>
>>> Are we OK to release 2.10.1?
>>>
>>>
>>> The main reason for doing this is to improve the error handling /
>>> reporting for the keytool utilities. I hope that is now OK.
>>
>> Seems to be, just wondering about 2 remaining cases:
>
> - certificate expiration
I think I tested that locally.
> - forced certificate removal, shouldn't we document somewhere which files
> to delete , jks, crt...
Done.
>>
>>>
>>>
>>> Are there any other fixes that must to go into the release?
>>
>>
> There is the one about redirect which after further analysis is not a real
> bug
> In versions below 2.10 we accepted non fully standard redirects, in 2.10 it
> was not more possible, as per our discussion we added a property to relax
> on rfc which defaults to true.
>
>
>>
>>> I don't think we should add any new functionality for this release.
>>
>>
>>> It's more important to get the keytool fixes deployed.
>>>
>>
> Well there are already some commited:
> - Xpath tester
> - JMs typed properties
> - ability to choose client certificate
> Plus a bunch of bug fixes and perf improvements.
>
>
> I suggest we name it 2.11 due to the previous features.
>
OK
>>
>> I agree with you.
>>
>>
>>> Anyone particularly want to be RM?
>>>
>>
>> I can act as RM. If we are ok, I can start the process today or tomorrow.
>>
> Milamber
>>
>>
>>>
>>
>
> --
> Cordialement.
> Philippe Mouawad.
Re: Release 2.10.1 ?
Posted by Philippe Mouawad <ph...@gmail.com>.
On Monday, December 30, 2013, Milamber wrote:
>
> Le 30/12/2013 02:03, sebb a ecrit :
>
>> Are we OK to release 2.10.1?
>>
>>
>> The main reason for doing this is to improve the error handling /
>> reporting for the keytool utilities. I hope that is now OK.
>
> Seems to be, just wondering about 2 remaining cases:
- certificate expiration
- forced certificate removal, shouldn't we document somewhere which files
to delete , jks, crt...
>
>>
>>
>> Are there any other fixes that must to go into the release?
>
>
There is the one about redirect which after further analysis is not a real
bug
In versions below 2.10 we accepted non fully standard redirects, in 2.10 it
was not more possible, as per our discussion we added a property to relax
on rfc which defaults to true.
>
>> I don't think we should add any new functionality for this release.
>
>
>> It's more important to get the keytool fixes deployed.
>>
>
Well there are already some commited:
- Xpath tester
- JMs typed properties
- ability to choose client certificate
Plus a bunch of bug fixes and perf improvements.
I suggest we name it 2.11 due to the previous features.
>
> I agree with you.
>
>
>> Anyone particularly want to be RM?
>>
>
> I can act as RM. If we are ok, I can start the process today or tomorrow.
>
Milamber
>
>
>>
>
--
Cordialement.
Philippe Mouawad.
Re: Release 2.10.1 ?
Posted by Milamber <mi...@apache.org>.
Le 31/12/2013 02:30, sebb a ecrit :
> On 30 December 2013 07:32, Milamber <mi...@apache.org> wrote:
>> Le 30/12/2013 02:03, sebb a ecrit :
>>
>>> Are we OK to release 2.10.1?
>>>
>>> The main reason for doing this is to improve the error handling /
>>> reporting for the keytool utilities. I hope that is now OK.
>>>
>>> Are there any other fixes that must to go into the release?
>>> I don't think we should add any new functionality for this release.
>>> It's more important to get the keytool fixes deployed.
>>
>> I agree with you.
>>
>>
>>> Anyone particularly want to be RM?
>>
>> I can act as RM. If we are ok, I can start the process today or tomorrow.
> Thanks very much.
>
> I think it would be best to call it 2.11, given that there have been
> enhancements added.
OK go to 2.11.
I will start the release process this afternoon (around 02:00 PM GMT)
>
>> Milamber
>>
Re: Release 2.10.1 ?
Posted by sebb <se...@gmail.com>.
On 30 December 2013 07:32, Milamber <mi...@apache.org> wrote:
>
> Le 30/12/2013 02:03, sebb a ecrit :
>
>> Are we OK to release 2.10.1?
>>
>> The main reason for doing this is to improve the error handling /
>> reporting for the keytool utilities. I hope that is now OK.
>>
>> Are there any other fixes that must to go into the release?
>> I don't think we should add any new functionality for this release.
>> It's more important to get the keytool fixes deployed.
>
>
> I agree with you.
>
>
>>
>> Anyone particularly want to be RM?
>
>
> I can act as RM. If we are ok, I can start the process today or tomorrow.
Thanks very much.
I think it would be best to call it 2.11, given that there have been
enhancements added.
> Milamber
>
>>
>
Re: Release 2.10.1 ?
Posted by Milamber <mi...@apache.org>.
Le 30/12/2013 02:03, sebb a ecrit :
> Are we OK to release 2.10.1?
>
> The main reason for doing this is to improve the error handling /
> reporting for the keytool utilities. I hope that is now OK.
>
> Are there any other fixes that must to go into the release?
> I don't think we should add any new functionality for this release.
> It's more important to get the keytool fixes deployed.
I agree with you.
>
> Anyone particularly want to be RM?
I can act as RM. If we are ok, I can start the process today or tomorrow.
Milamber
>