Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

Hi All,
Thoughts on this ?

Thanks

On Friday, March 25, 2016, Philippe Mouawad 
wrote:

> Hello,
> Nothing I am aware of. I've been tracking those items closely.
> Regards
>
> On Thu, Mar 24, 2016 at 11:45 PM, sebb  > wrote:
>
>> Are there any remaining issues with the latest version of HC?
>> I've not really been following that much.
>>
>> On 24 March 2016 at 21:40, Philippe Mouawad > > wrote:
>> > Hello,
>> > Am I wrong to think that we are now nearly ready to start a release , I
>> see
>> > those remaining issues:
>> > https://bz.apache.org/bugzilla/show_bug.cgi?id=59171 : Sebb is waiting
>> for
>> > feedback. I provided mine
>> > https://bz.apache.org/bugzilla/show_bug.cgi?id=59173 : Sebb fixed the
>> > issue. We had a discussion on the BackendListener. It's not a blocker
>> for me
>> >
>> > The last other issues are all related to documentation.
>> >
>> > If we agree to start the release process I can start working on New and
>> > Noteworthy section and update some screenshots.
>> >
>> > We are now more than 1 year from 2.13 release, I think it's time for a
>> > release.
>> >
>> > Thoughts ?
>> >
>> > Regards
>> > Philippe
>> >
>> > On Thu, Mar 17, 2016 at 8:25 PM, Philippe Mouawad <
>> > philippe.moua...@gmail.com
>> > wrote:
>> >
>> >>
>> >>
>> >> On Thu, Mar 17, 2016 at 6:10 PM, sebb > > wrote:
>> >>
>> >>> On 17 March 2016 at 16:59, Philippe Mouawad <
>> philippe.moua...@gmail.com
>> >
>> >>> wrote:
>> >>> > Hi sebb,
>> >>> > I have fixed 1/4 issues reported in 59173 and think other "issues"
>> >>> should
>> >>> > be mentioned in changes and not fixed as I think some cannot be
>> without
>> >>> > important work without real ROI.
>> >>>
>> >>> ? cannot parse.
>> >>>
>> >> I don't understand.
>> >> Can you read my comment
>> >> https://bz.apache.org/bugzilla/show_bug.cgi?id=59173#c4
>> >>
>> >>>
>> >>> > Regarding 58832, it's a minor issue without effect as report works
>> and
>> >>> > displays fine under ff, chrome, safari and IE and generation works
>> fine
>> >>> on
>> >>> > windows, linux and macosx.
>> >>> > So unless you have an issue with it that you clearly find as
>> blocker I
>> >>> > don't think it should delay release.
>> >>>
>> >>> I've already renamed the files and marked the bug fixed.
>> >>>
>> >>
>> >> Great I missed it.
>> >>
>> >>>
>> >>> > Can you answer my question on output report in the bugzilla your
>> >>> reopened ?
>> >>> > so that I can proceed withfix ?
>> >>>
>> >>> What question?
>> >>>
>> >>
>> >> The one in this big thread:
>> >> "for the output of reports, check that if -o is not used the default
>> >> target folder is not overwritten if not empty. I propose to delay other
>> >> propositions to next 3.1 and wait for user feedback. I can take it
>> unless
>> >> sebb you want to "
>> >>
>> >>
>> >>
>> >>> > Finally regarding the order of columns in the Save configuration,
>> you
>> >>> > commited something but issue is not in changes nor resolved, what's
>> the
>> >>> > status on it ?
>> >>>
>> >>> Waiting for review to see if the order is sensible or not.
>> >>> We don't want to change it unnecessarily later.
>> >>>
>> >> Ok
>> >>
>> >>>
>> >>> Also note that various new jars need to be mentioned in LICENSE.
>> >>>
>> >> Fixed
>> >>
>> >>> This assumes that their licenses are compatible; I've not seen any
>> >>> analysis of them.
>> >>>
>> >> Yes, analysis was made but I forgot to add the license for asm, done
>> now
>> >>
>> >>>
>> >>> > Thanks
>> >>> >
>> >>> > On Wednesday, March 16, 2016, sebb > > wrote:
>> >>> >
>> >>> >> There are some regressions/new bugs:
>> >>> >>
>> >>> >> Bug 59173
>> >>> >>
>> >>> >> Bug 58832
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> On 16 March 2016 at 19:16, Philippe Mouawad <
>> >>> philippe.moua...@gmail.com
>> 
>> >>> >> > wrote:
>> >>> >> > Hi sebb,
>> >>> >> > With the last commits and comments on the issues you mentioned,
>> >>> >> > can we consider that remaining work is the following:
>> >>> >> > - sort the columns of saved columns per english translation : you
>> >>> seem to
>> >>> >> > be handling it
>> >>> >> > - for the output of reports, check that if -o is not used the
>> default
>> >>> >> > target folder is not overwritten if not empty. I propose to delay
>> >>> other
>> >>> >> > propositions to next 3.1 and wait for user feedback. I can take
>> it
>> >>> unless
>> >>> >> > sebb you want to
>> >>> >> > - fix the NTLM auth issue with https: Felix can you confirm you
>> will
>> >>> be
>> >>> >> > able to fix it in a 

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

Hello,
Nothing I am aware of. I've been tracking those items closely.
Regards

On Thu, Mar 24, 2016 at 11:45 PM, sebb  wrote:

> Are there any remaining issues with the latest version of HC?
> I've not really been following that much.
>
> On 24 March 2016 at 21:40, Philippe Mouawad 
> wrote:
> > Hello,
> > Am I wrong to think that we are now nearly ready to start a release , I
> see
> > those remaining issues:
> > https://bz.apache.org/bugzilla/show_bug.cgi?id=59171 : Sebb is waiting
> for
> > feedback. I provided mine
> > https://bz.apache.org/bugzilla/show_bug.cgi?id=59173 : Sebb fixed the
> > issue. We had a discussion on the BackendListener. It's not a blocker
> for me
> >
> > The last other issues are all related to documentation.
> >
> > If we agree to start the release process I can start working on New and
> > Noteworthy section and update some screenshots.
> >
> > We are now more than 1 year from 2.13 release, I think it's time for a
> > release.
> >
> > Thoughts ?
> >
> > Regards
> > Philippe
> >
> > On Thu, Mar 17, 2016 at 8:25 PM, Philippe Mouawad <
> > philippe.moua...@gmail.com> wrote:
> >
> >>
> >>
> >> On Thu, Mar 17, 2016 at 6:10 PM, sebb  wrote:
> >>
> >>> On 17 March 2016 at 16:59, Philippe Mouawad <
> philippe.moua...@gmail.com>
> >>> wrote:
> >>> > Hi sebb,
> >>> > I have fixed 1/4 issues reported in 59173 and think other "issues"
> >>> should
> >>> > be mentioned in changes and not fixed as I think some cannot be
> without
> >>> > important work without real ROI.
> >>>
> >>> ? cannot parse.
> >>>
> >> I don't understand.
> >> Can you read my comment
> >> https://bz.apache.org/bugzilla/show_bug.cgi?id=59173#c4
> >>
> >>>
> >>> > Regarding 58832, it's a minor issue without effect as report works
> and
> >>> > displays fine under ff, chrome, safari and IE and generation works
> fine
> >>> on
> >>> > windows, linux and macosx.
> >>> > So unless you have an issue with it that you clearly find as blocker
> I
> >>> > don't think it should delay release.
> >>>
> >>> I've already renamed the files and marked the bug fixed.
> >>>
> >>
> >> Great I missed it.
> >>
> >>>
> >>> > Can you answer my question on output report in the bugzilla your
> >>> reopened ?
> >>> > so that I can proceed withfix ?
> >>>
> >>> What question?
> >>>
> >>
> >> The one in this big thread:
> >> "for the output of reports, check that if -o is not used the default
> >> target folder is not overwritten if not empty. I propose to delay other
> >> propositions to next 3.1 and wait for user feedback. I can take it
> unless
> >> sebb you want to "
> >>
> >>
> >>
> >>> > Finally regarding the order of columns in the Save configuration, you
> >>> > commited something but issue is not in changes nor resolved, what's
> the
> >>> > status on it ?
> >>>
> >>> Waiting for review to see if the order is sensible or not.
> >>> We don't want to change it unnecessarily later.
> >>>
> >> Ok
> >>
> >>>
> >>> Also note that various new jars need to be mentioned in LICENSE.
> >>>
> >> Fixed
> >>
> >>> This assumes that their licenses are compatible; I've not seen any
> >>> analysis of them.
> >>>
> >> Yes, analysis was made but I forgot to add the license for asm, done now
> >>
> >>>
> >>> > Thanks
> >>> >
> >>> > On Wednesday, March 16, 2016, sebb  wrote:
> >>> >
> >>> >> There are some regressions/new bugs:
> >>> >>
> >>> >> Bug 59173
> >>> >>
> >>> >> Bug 58832
> >>> >>
> >>> >>
> >>> >>
> >>> >> On 16 March 2016 at 19:16, Philippe Mouawad <
> >>> philippe.moua...@gmail.com
> >>> >> > wrote:
> >>> >> > Hi sebb,
> >>> >> > With the last commits and comments on the issues you mentioned,
> >>> >> > can we consider that remaining work is the following:
> >>> >> > - sort the columns of saved columns per english translation : you
> >>> seem to
> >>> >> > be handling it
> >>> >> > - for the output of reports, check that if -o is not used the
> default
> >>> >> > target folder is not overwritten if not empty. I propose to delay
> >>> other
> >>> >> > propositions to next 3.1 and wait for user feedback. I can take it
> >>> unless
> >>> >> > sebb you want to
> >>> >> > - fix the NTLM auth issue with https: Felix can you confirm you
> will
> >>> be
> >>> >> > able to fix it in a not too big delay ?
> >>> >> > - screenshots for all modified elements, volunteers ?
> >>> >> > - new and noteworthy section, I can start it
> >>> >> >
> >>> >> >
> >>> >> > We're now 1 year since we released 2.13, I think users are waiting
> >>> this
> >>> >> 3.0
> >>> >> > .
> >>> >> >
> >>> >> > I am as a user
> >>> >> >
> >>> >> >
> >>> >> > Thanks
> >>> >> > On Tuesday, March 15, 2016, Philippe Mouawad <
> >>> philippe.moua...@gmail.com
> >>> >> >
> >>> >> > wrote:
> >>> >> >
> >>> >> >>
> >>> >> >>
> >>> >> >> On Tue, Mar 15, 2016 at 9:45 PM, Felix Schumacher <
> >>> >> >> felix.schumac...@internetallee.de 
> >>> >> >> 

Re: Remaining Work before Release of 3.0

[sebb]

Are there any remaining issues with the latest version of HC?
I've not really been following that much.

On 24 March 2016 at 21:40, Philippe Mouawad  wrote:
> Hello,
> Am I wrong to think that we are now nearly ready to start a release , I see
> those remaining issues:
> https://bz.apache.org/bugzilla/show_bug.cgi?id=59171 : Sebb is waiting for
> feedback. I provided mine
> https://bz.apache.org/bugzilla/show_bug.cgi?id=59173 : Sebb fixed the
> issue. We had a discussion on the BackendListener. It's not a blocker for me
>
> The last other issues are all related to documentation.
>
> If we agree to start the release process I can start working on New and
> Noteworthy section and update some screenshots.
>
> We are now more than 1 year from 2.13 release, I think it's time for a
> release.
>
> Thoughts ?
>
> Regards
> Philippe
>
> On Thu, Mar 17, 2016 at 8:25 PM, Philippe Mouawad <
> philippe.moua...@gmail.com> wrote:
>
>>
>>
>> On Thu, Mar 17, 2016 at 6:10 PM, sebb  wrote:
>>
>>> On 17 March 2016 at 16:59, Philippe Mouawad 
>>> wrote:
>>> > Hi sebb,
>>> > I have fixed 1/4 issues reported in 59173 and think other "issues"
>>> should
>>> > be mentioned in changes and not fixed as I think some cannot be without
>>> > important work without real ROI.
>>>
>>> ? cannot parse.
>>>
>> I don't understand.
>> Can you read my comment
>> https://bz.apache.org/bugzilla/show_bug.cgi?id=59173#c4
>>
>>>
>>> > Regarding 58832, it's a minor issue without effect as report works and
>>> > displays fine under ff, chrome, safari and IE and generation works fine
>>> on
>>> > windows, linux and macosx.
>>> > So unless you have an issue with it that you clearly find as blocker I
>>> > don't think it should delay release.
>>>
>>> I've already renamed the files and marked the bug fixed.
>>>
>>
>> Great I missed it.
>>
>>>
>>> > Can you answer my question on output report in the bugzilla your
>>> reopened ?
>>> > so that I can proceed withfix ?
>>>
>>> What question?
>>>
>>
>> The one in this big thread:
>> "for the output of reports, check that if -o is not used the default
>> target folder is not overwritten if not empty. I propose to delay other
>> propositions to next 3.1 and wait for user feedback. I can take it unless
>> sebb you want to "
>>
>>
>>
>>> > Finally regarding the order of columns in the Save configuration, you
>>> > commited something but issue is not in changes nor resolved, what's the
>>> > status on it ?
>>>
>>> Waiting for review to see if the order is sensible or not.
>>> We don't want to change it unnecessarily later.
>>>
>> Ok
>>
>>>
>>> Also note that various new jars need to be mentioned in LICENSE.
>>>
>> Fixed
>>
>>> This assumes that their licenses are compatible; I've not seen any
>>> analysis of them.
>>>
>> Yes, analysis was made but I forgot to add the license for asm, done now
>>
>>>
>>> > Thanks
>>> >
>>> > On Wednesday, March 16, 2016, sebb  wrote:
>>> >
>>> >> There are some regressions/new bugs:
>>> >>
>>> >> Bug 59173
>>> >>
>>> >> Bug 58832
>>> >>
>>> >>
>>> >>
>>> >> On 16 March 2016 at 19:16, Philippe Mouawad <
>>> philippe.moua...@gmail.com
>>> >> > wrote:
>>> >> > Hi sebb,
>>> >> > With the last commits and comments on the issues you mentioned,
>>> >> > can we consider that remaining work is the following:
>>> >> > - sort the columns of saved columns per english translation : you
>>> seem to
>>> >> > be handling it
>>> >> > - for the output of reports, check that if -o is not used the default
>>> >> > target folder is not overwritten if not empty. I propose to delay
>>> other
>>> >> > propositions to next 3.1 and wait for user feedback. I can take it
>>> unless
>>> >> > sebb you want to
>>> >> > - fix the NTLM auth issue with https: Felix can you confirm you will
>>> be
>>> >> > able to fix it in a not too big delay ?
>>> >> > - screenshots for all modified elements, volunteers ?
>>> >> > - new and noteworthy section, I can start it
>>> >> >
>>> >> >
>>> >> > We're now 1 year since we released 2.13, I think users are waiting
>>> this
>>> >> 3.0
>>> >> > .
>>> >> >
>>> >> > I am as a user
>>> >> >
>>> >> >
>>> >> > Thanks
>>> >> > On Tuesday, March 15, 2016, Philippe Mouawad <
>>> philippe.moua...@gmail.com
>>> >> >
>>> >> > wrote:
>>> >> >
>>> >> >>
>>> >> >>
>>> >> >> On Tue, Mar 15, 2016 at 9:45 PM, Felix Schumacher <
>>> >> >> felix.schumac...@internetallee.de 
>>> >> >> >> >> ');>>
>>> >> >> wrote:
>>> >> >>
>>> >> >>>
>>> >> >>>
>>> >> >>> Am 14. März 2016 21:58:50 MEZ, schrieb Philippe Mouawad <
>>> >> >>> philippe.moua...@gmail.com 
>>> >> >>> >> >> ');>>:
>>> >> >>> >On Monday, March 14, 2016, Felix Schumacher <
>>> >> >>> >felix.schumac...@internetallee.de 
>>> >> >>> 

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

Hello,
Am I wrong to think that we are now nearly ready to start a release , I see
those remaining issues:
https://bz.apache.org/bugzilla/show_bug.cgi?id=59171 : Sebb is waiting for
feedback. I provided mine
https://bz.apache.org/bugzilla/show_bug.cgi?id=59173 : Sebb fixed the
issue. We had a discussion on the BackendListener. It's not a blocker for me

The last other issues are all related to documentation.

If we agree to start the release process I can start working on New and
Noteworthy section and update some screenshots.

We are now more than 1 year from 2.13 release, I think it's time for a
release.

Thoughts ?

Regards
Philippe

On Thu, Mar 17, 2016 at 8:25 PM, Philippe Mouawad <
philippe.moua...@gmail.com> wrote:

>
>
> On Thu, Mar 17, 2016 at 6:10 PM, sebb  wrote:
>
>> On 17 March 2016 at 16:59, Philippe Mouawad 
>> wrote:
>> > Hi sebb,
>> > I have fixed 1/4 issues reported in 59173 and think other "issues"
>> should
>> > be mentioned in changes and not fixed as I think some cannot be without
>> > important work without real ROI.
>>
>> ? cannot parse.
>>
> I don't understand.
> Can you read my comment
> https://bz.apache.org/bugzilla/show_bug.cgi?id=59173#c4
>
>>
>> > Regarding 58832, it's a minor issue without effect as report works and
>> > displays fine under ff, chrome, safari and IE and generation works fine
>> on
>> > windows, linux and macosx.
>> > So unless you have an issue with it that you clearly find as blocker I
>> > don't think it should delay release.
>>
>> I've already renamed the files and marked the bug fixed.
>>
>
> Great I missed it.
>
>>
>> > Can you answer my question on output report in the bugzilla your
>> reopened ?
>> > so that I can proceed withfix ?
>>
>> What question?
>>
>
> The one in this big thread:
> "for the output of reports, check that if -o is not used the default
> target folder is not overwritten if not empty. I propose to delay other
> propositions to next 3.1 and wait for user feedback. I can take it unless
> sebb you want to "
>
>
>
>> > Finally regarding the order of columns in the Save configuration, you
>> > commited something but issue is not in changes nor resolved, what's the
>> > status on it ?
>>
>> Waiting for review to see if the order is sensible or not.
>> We don't want to change it unnecessarily later.
>>
> Ok
>
>>
>> Also note that various new jars need to be mentioned in LICENSE.
>>
> Fixed
>
>> This assumes that their licenses are compatible; I've not seen any
>> analysis of them.
>>
> Yes, analysis was made but I forgot to add the license for asm, done now
>
>>
>> > Thanks
>> >
>> > On Wednesday, March 16, 2016, sebb  wrote:
>> >
>> >> There are some regressions/new bugs:
>> >>
>> >> Bug 59173
>> >>
>> >> Bug 58832
>> >>
>> >>
>> >>
>> >> On 16 March 2016 at 19:16, Philippe Mouawad <
>> philippe.moua...@gmail.com
>> >> > wrote:
>> >> > Hi sebb,
>> >> > With the last commits and comments on the issues you mentioned,
>> >> > can we consider that remaining work is the following:
>> >> > - sort the columns of saved columns per english translation : you
>> seem to
>> >> > be handling it
>> >> > - for the output of reports, check that if -o is not used the default
>> >> > target folder is not overwritten if not empty. I propose to delay
>> other
>> >> > propositions to next 3.1 and wait for user feedback. I can take it
>> unless
>> >> > sebb you want to
>> >> > - fix the NTLM auth issue with https: Felix can you confirm you will
>> be
>> >> > able to fix it in a not too big delay ?
>> >> > - screenshots for all modified elements, volunteers ?
>> >> > - new and noteworthy section, I can start it
>> >> >
>> >> >
>> >> > We're now 1 year since we released 2.13, I think users are waiting
>> this
>> >> 3.0
>> >> > .
>> >> >
>> >> > I am as a user
>> >> >
>> >> >
>> >> > Thanks
>> >> > On Tuesday, March 15, 2016, Philippe Mouawad <
>> philippe.moua...@gmail.com
>> >> >
>> >> > wrote:
>> >> >
>> >> >>
>> >> >>
>> >> >> On Tue, Mar 15, 2016 at 9:45 PM, Felix Schumacher <
>> >> >> felix.schumac...@internetallee.de 
>> >> >> > >> ');>>
>> >> >> wrote:
>> >> >>
>> >> >>>
>> >> >>>
>> >> >>> Am 14. März 2016 21:58:50 MEZ, schrieb Philippe Mouawad <
>> >> >>> philippe.moua...@gmail.com 
>> >> >>> > >> ');>>:
>> >> >>> >On Monday, March 14, 2016, Felix Schumacher <
>> >> >>> >felix.schumac...@internetallee.de 
>> >> >>> > >> ');>>
>> >> >>> wrote:
>> >> >>> >
>> >> >>> >> Am 14.03.2016 um 21:34 schrieb Philippe Mouawad:
>> >> >>> >>
>> >> >>> >>> Hello,
>> >> >>> >>> All remaining issues before 3.0 are now fixed.
>> >> >>> >>>
>> >> >>> >> https://issues.apache.org/jira/browse/HTTPCLIENT-1712
>> >> 

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

Hi sebb,
With the last commits and comments on the issues you mentioned,
can we consider that remaining work is the following:
- sort the columns of saved columns per english translation : you seem to
be handling it
- for the output of reports, check that if -o is not used the default
target folder is not overwritten if not empty. I propose to delay other
propositions to next 3.1 and wait for user feedback. I can take it unless
sebb you want to
- fix the NTLM auth issue with https: Felix can you confirm you will be
able to fix it in a not too big delay ?
- screenshots for all modified elements, volunteers ?
- new and noteworthy section, I can start it


We're now 1 year since we released 2.13, I think users are waiting this 3.0
.

I am as a user


Thanks
On Tuesday, March 15, 2016, Philippe Mouawad 
wrote:

>
>
> On Tue, Mar 15, 2016 at 9:45 PM, Felix Schumacher <
> felix.schumac...@internetallee.de
> >
> wrote:
>
>>
>>
>> Am 14. März 2016 21:58:50 MEZ, schrieb Philippe Mouawad <
>> philippe.moua...@gmail.com
>> >:
>> >On Monday, March 14, 2016, Felix Schumacher <
>> >felix.schumac...@internetallee.de
>> >
>> wrote:
>> >
>> >> Am 14.03.2016 um 21:34 schrieb Philippe Mouawad:
>> >>
>> >>> Hello,
>> >>> All remaining issues before 3.0 are now fixed.
>> >>>
>> >> https://issues.apache.org/jira/browse/HTTPCLIENT-1712
>> >> means that we can't do kerberos with https. Is this a big problem?
>> >
>> >
>> >are we able to workaround in jmeter the issue ?
>> >If not it would mean we have to wait for a 4.5.3
>> >
>> >It does not seem critical for me but I don't know
>>
>> We could work around it. We would have to subclass two classes.
>> SPnegoScheme and its factory.
>>
> Let's do that Felix if you think we need to fix it before 3.0.
>
>>
>> The problem is fixed in httpclients trunk, but I don't know when a next
>> release is planned.
>>
>
> 4.5.2 was just released, I doubt a new one will be released for such a bug
>
>
>>
>> Felix
>>
>> >
>> >>
>> >> Felix
>> >>
>> >>>
>> >>> Except for the documentation screenshots everything is ready for a
>> >>> release.
>> >>>
>> >>> When do we launch the release of 3.0 ?
>> >>>
>> >>> Regards
>> >>> Philippe
>> >>>
>> >>>
>> >>> On Fri, Mar 11, 2016 at 8:20 AM, Milamber > >
>> >wrote:
>> >>>
>> >>>
>>  On 08/03/2016 23:02, Philippe Mouawad wrote:
>> 
>>  @Milamber, do you intend to take into account before 3.0 release
>> >the
>> > notes
>> > from Benoit Wiart:
>> > -https://bz.apache.org/bugzilla/show_bug.cgi?id=58426
>> >
>> > Not before the 3.0.
>> 
>> 
>>  If not, I suggest we close this one and open a new one to complete
>> >HiDPI
>> > support in 3.1
>> >
>> > That seems a good idea.
>> 
>> 
>>  Milamber
>> 
>> 
>> >>>
>> >>>
>> >>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>

-- 
Cordialement.
Philippe Mouawad.

Re: Remaining Work before Release of 3.0

[Felix Schumacher]

Am 16. März 2016 20:16:22 MEZ, schrieb Philippe Mouawad 
:
>Hi sebb,
>With the last commits and comments on the issues you mentioned,
>can we consider that remaining work is the following:
>- sort the columns of saved columns per english translation : you seem
>to
>be handling it
>- for the output of reports, check that if -o is not used the default
>target folder is not overwritten if not empty. I propose to delay other
>propositions to next 3.1 and wait for user feedback. I can take it
>unless
>sebb you want to
>- fix the NTLM auth issue with https: Felix can you confirm you will be
>able to fix it in a not too big delay ?

It's kerberos and I can do it probably tonight. 

Felix

>- screenshots for all modified elements, volunteers ?
>- new and noteworthy section, I can start it
>
>
>We're now 1 year since we released 2.13, I think users are waiting this
>3.0
>.
>
>I am as a user
>
>
>Thanks
>On Tuesday, March 15, 2016, Philippe Mouawad
>
>wrote:
>
>>
>>
>> On Tue, Mar 15, 2016 at 9:45 PM, Felix Schumacher <
>> felix.schumac...@internetallee.de
>> >
>> wrote:
>>
>>>
>>>
>>> Am 14. März 2016 21:58:50 MEZ, schrieb Philippe Mouawad <
>>> philippe.moua...@gmail.com
>>> >:
>>> >On Monday, March 14, 2016, Felix Schumacher <
>>> >felix.schumac...@internetallee.de
>>> >
>>> wrote:
>>> >
>>> >> Am 14.03.2016 um 21:34 schrieb Philippe Mouawad:
>>> >>
>>> >>> Hello,
>>> >>> All remaining issues before 3.0 are now fixed.
>>> >>>
>>> >> https://issues.apache.org/jira/browse/HTTPCLIENT-1712
>>> >> means that we can't do kerberos with https. Is this a big
>problem?
>>> >
>>> >
>>> >are we able to workaround in jmeter the issue ?
>>> >If not it would mean we have to wait for a 4.5.3
>>> >
>>> >It does not seem critical for me but I don't know
>>>
>>> We could work around it. We would have to subclass two classes.
>>> SPnegoScheme and its factory.
>>>
>> Let's do that Felix if you think we need to fix it before 3.0.
>>
>>>
>>> The problem is fixed in httpclients trunk, but I don't know when a
>next
>>> release is planned.
>>>
>>
>> 4.5.2 was just released, I doubt a new one will be released for such
>a bug
>>
>>
>>>
>>> Felix
>>>
>>> >
>>> >>
>>> >> Felix
>>> >>
>>> >>>
>>> >>> Except for the documentation screenshots everything is ready for
>a
>>> >>> release.
>>> >>>
>>> >>> When do we launch the release of 3.0 ?
>>> >>>
>>> >>> Regards
>>> >>> Philippe
>>> >>>
>>> >>>
>>> >>> On Fri, Mar 11, 2016 at 8:20 AM, Milamber >> >
>>> >wrote:
>>> >>>
>>> >>>
>>>  On 08/03/2016 23:02, Philippe Mouawad wrote:
>>> 
>>>  @Milamber, do you intend to take into account before 3.0
>release
>>> >the
>>> > notes
>>> > from Benoit Wiart:
>>> > -https://bz.apache.org/bugzilla/show_bug.cgi?id=58426
>>> >
>>> > Not before the 3.0.
>>> 
>>> 
>>>  If not, I suggest we close this one and open a new one to
>complete
>>> >HiDPI
>>> > support in 3.1
>>> >
>>> > That seems a good idea.
>>> 
>>> 
>>>  Milamber
>>> 
>>> 
>>> >>>
>>> >>>
>>> >>
>>>
>>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

On Thu, Mar 17, 2016 at 6:10 PM, sebb  wrote:

> On 17 March 2016 at 16:59, Philippe Mouawad 
> wrote:
> > Hi sebb,
> > I have fixed 1/4 issues reported in 59173 and think other "issues" should
> > be mentioned in changes and not fixed as I think some cannot be without
> > important work without real ROI.
>
> ? cannot parse.
>
I don't understand.
Can you read my comment
https://bz.apache.org/bugzilla/show_bug.cgi?id=59173#c4

>
> > Regarding 58832, it's a minor issue without effect as report works and
> > displays fine under ff, chrome, safari and IE and generation works fine
> on
> > windows, linux and macosx.
> > So unless you have an issue with it that you clearly find as blocker I
> > don't think it should delay release.
>
> I've already renamed the files and marked the bug fixed.
>

Great I missed it.

>
> > Can you answer my question on output report in the bugzilla your
> reopened ?
> > so that I can proceed withfix ?
>
> What question?
>

The one in this big thread:
"for the output of reports, check that if -o is not used the default target
folder is not overwritten if not empty. I propose to delay other
propositions to next 3.1 and wait for user feedback. I can take it unless
sebb you want to "



> > Finally regarding the order of columns in the Save configuration, you
> > commited something but issue is not in changes nor resolved, what's the
> > status on it ?
>
> Waiting for review to see if the order is sensible or not.
> We don't want to change it unnecessarily later.
>
Ok

>
> Also note that various new jars need to be mentioned in LICENSE.
>
Fixed

> This assumes that their licenses are compatible; I've not seen any
> analysis of them.
>
Yes, analysis was made but I forgot to add the license for asm, done now

>
> > Thanks
> >
> > On Wednesday, March 16, 2016, sebb  wrote:
> >
> >> There are some regressions/new bugs:
> >>
> >> Bug 59173
> >>
> >> Bug 58832
> >>
> >>
> >>
> >> On 16 March 2016 at 19:16, Philippe Mouawad  >> > wrote:
> >> > Hi sebb,
> >> > With the last commits and comments on the issues you mentioned,
> >> > can we consider that remaining work is the following:
> >> > - sort the columns of saved columns per english translation : you
> seem to
> >> > be handling it
> >> > - for the output of reports, check that if -o is not used the default
> >> > target folder is not overwritten if not empty. I propose to delay
> other
> >> > propositions to next 3.1 and wait for user feedback. I can take it
> unless
> >> > sebb you want to
> >> > - fix the NTLM auth issue with https: Felix can you confirm you will
> be
> >> > able to fix it in a not too big delay ?
> >> > - screenshots for all modified elements, volunteers ?
> >> > - new and noteworthy section, I can start it
> >> >
> >> >
> >> > We're now 1 year since we released 2.13, I think users are waiting
> this
> >> 3.0
> >> > .
> >> >
> >> > I am as a user
> >> >
> >> >
> >> > Thanks
> >> > On Tuesday, March 15, 2016, Philippe Mouawad <
> philippe.moua...@gmail.com
> >> >
> >> > wrote:
> >> >
> >> >>
> >> >>
> >> >> On Tue, Mar 15, 2016 at 9:45 PM, Felix Schumacher <
> >> >> felix.schumac...@internetallee.de 
> >> >>  >> ');>>
> >> >> wrote:
> >> >>
> >> >>>
> >> >>>
> >> >>> Am 14. März 2016 21:58:50 MEZ, schrieb Philippe Mouawad <
> >> >>> philippe.moua...@gmail.com 
> >> >>>  >> ');>>:
> >> >>> >On Monday, March 14, 2016, Felix Schumacher <
> >> >>> >felix.schumac...@internetallee.de 
> >> >>>  >> ');>>
> >> >>> wrote:
> >> >>> >
> >> >>> >> Am 14.03.2016 um 21:34 schrieb Philippe Mouawad:
> >> >>> >>
> >> >>> >>> Hello,
> >> >>> >>> All remaining issues before 3.0 are now fixed.
> >> >>> >>>
> >> >>> >> https://issues.apache.org/jira/browse/HTTPCLIENT-1712
> >> >>> >> means that we can't do kerberos with https. Is this a big
> problem?
> >> >>> >
> >> >>> >
> >> >>> >are we able to workaround in jmeter the issue ?
> >> >>> >If not it would mean we have to wait for a 4.5.3
> >> >>> >
> >> >>> >It does not seem critical for me but I don't know
> >> >>>
> >> >>> We could work around it. We would have to subclass two classes.
> >> >>> SPnegoScheme and its factory.
> >> >>>
> >> >> Let's do that Felix if you think we need to fix it before 3.0.
> >> >>
> >> >>>
> >> >>> The problem is fixed in httpclients trunk, but I don't know when a
> next
> >> >>> release is planned.
> >> >>>
> >> >>
> >> >> 4.5.2 was just released, I doubt a new one will be released for such
> a
> >> bug
> >> >>
> >> >>
> >> >>>
> >> >>> Felix
> >> >>>
> >> >>> >
> >> >>> >>
> >> >>> >> Felix
> >> >>> >>
> >> >>> >>>
> >> >>> >>> Except for the documentation screenshots 

Re: Remaining Work before Release of 3.0

[sebb]

On 17 March 2016 at 16:59, Philippe Mouawad  wrote:
> Hi sebb,
> I have fixed 1/4 issues reported in 59173 and think other "issues" should
> be mentioned in changes and not fixed as I think some cannot be without
> important work without real ROI.

? cannot parse.

> Regarding 58832, it's a minor issue without effect as report works and
> displays fine under ff, chrome, safari and IE and generation works fine on
> windows, linux and macosx.
> So unless you have an issue with it that you clearly find as blocker I
> don't think it should delay release.

I've already renamed the files and marked the bug fixed.

> Can you answer my question on output report in the bugzilla your reopened ?
> so that I can proceed withfix ?

What question?

> Finally regarding the order of columns in the Save configuration, you
> commited something but issue is not in changes nor resolved, what's the
> status on it ?

Waiting for review to see if the order is sensible or not.
We don't want to change it unnecessarily later.

Also note that various new jars need to be mentioned in LICENSE.
This assumes that their licenses are compatible; I've not seen any
analysis of them.

> Thanks
>
> On Wednesday, March 16, 2016, sebb  wrote:
>
>> There are some regressions/new bugs:
>>
>> Bug 59173
>>
>> Bug 58832
>>
>>
>>
>> On 16 March 2016 at 19:16, Philippe Mouawad > > wrote:
>> > Hi sebb,
>> > With the last commits and comments on the issues you mentioned,
>> > can we consider that remaining work is the following:
>> > - sort the columns of saved columns per english translation : you seem to
>> > be handling it
>> > - for the output of reports, check that if -o is not used the default
>> > target folder is not overwritten if not empty. I propose to delay other
>> > propositions to next 3.1 and wait for user feedback. I can take it unless
>> > sebb you want to
>> > - fix the NTLM auth issue with https: Felix can you confirm you will be
>> > able to fix it in a not too big delay ?
>> > - screenshots for all modified elements, volunteers ?
>> > - new and noteworthy section, I can start it
>> >
>> >
>> > We're now 1 year since we released 2.13, I think users are waiting this
>> 3.0
>> > .
>> >
>> > I am as a user
>> >
>> >
>> > Thanks
>> > On Tuesday, March 15, 2016, Philippe Mouawad > >
>> > wrote:
>> >
>> >>
>> >>
>> >> On Tue, Mar 15, 2016 at 9:45 PM, Felix Schumacher <
>> >> felix.schumac...@internetallee.de 
>> >> > ');>>
>> >> wrote:
>> >>
>> >>>
>> >>>
>> >>> Am 14. März 2016 21:58:50 MEZ, schrieb Philippe Mouawad <
>> >>> philippe.moua...@gmail.com 
>> >>> > ');>>:
>> >>> >On Monday, March 14, 2016, Felix Schumacher <
>> >>> >felix.schumac...@internetallee.de 
>> >>> > ');>>
>> >>> wrote:
>> >>> >
>> >>> >> Am 14.03.2016 um 21:34 schrieb Philippe Mouawad:
>> >>> >>
>> >>> >>> Hello,
>> >>> >>> All remaining issues before 3.0 are now fixed.
>> >>> >>>
>> >>> >> https://issues.apache.org/jira/browse/HTTPCLIENT-1712
>> >>> >> means that we can't do kerberos with https. Is this a big problem?
>> >>> >
>> >>> >
>> >>> >are we able to workaround in jmeter the issue ?
>> >>> >If not it would mean we have to wait for a 4.5.3
>> >>> >
>> >>> >It does not seem critical for me but I don't know
>> >>>
>> >>> We could work around it. We would have to subclass two classes.
>> >>> SPnegoScheme and its factory.
>> >>>
>> >> Let's do that Felix if you think we need to fix it before 3.0.
>> >>
>> >>>
>> >>> The problem is fixed in httpclients trunk, but I don't know when a next
>> >>> release is planned.
>> >>>
>> >>
>> >> 4.5.2 was just released, I doubt a new one will be released for such a
>> bug
>> >>
>> >>
>> >>>
>> >>> Felix
>> >>>
>> >>> >
>> >>> >>
>> >>> >> Felix
>> >>> >>
>> >>> >>>
>> >>> >>> Except for the documentation screenshots everything is ready for a
>> >>> >>> release.
>> >>> >>>
>> >>> >>> When do we launch the release of 3.0 ?
>> >>> >>>
>> >>> >>> Regards
>> >>> >>> Philippe
>> >>> >>>
>> >>> >>>
>> >>> >>> On Fri, Mar 11, 2016 at 8:20 AM, Milamber > 
>> >>> ');>>
>> >>> >wrote:
>> >>> >>>
>> >>> >>>
>> >>>  On 08/03/2016 23:02, Philippe Mouawad wrote:
>> >>> 
>> >>>  @Milamber, do you intend to take into account before 3.0 release
>> >>> >the
>> >>> > notes
>> >>> > from Benoit Wiart:
>> >>> > -https://bz.apache.org/bugzilla/show_bug.cgi?id=58426
>> >>> >
>> >>> > Not before the 3.0.
>> >>> 
>> >>> 
>> >>>  If not, I suggest we close this one and open a new one to complete
>> >>> >HiDPI
>> 

Re: Remaining Work before Release of 3.0

[sebb]

There are some regressions/new bugs:

Bug 59173

Bug 58832



On 16 March 2016 at 19:16, Philippe Mouawad  wrote:
> Hi sebb,
> With the last commits and comments on the issues you mentioned,
> can we consider that remaining work is the following:
> - sort the columns of saved columns per english translation : you seem to
> be handling it
> - for the output of reports, check that if -o is not used the default
> target folder is not overwritten if not empty. I propose to delay other
> propositions to next 3.1 and wait for user feedback. I can take it unless
> sebb you want to
> - fix the NTLM auth issue with https: Felix can you confirm you will be
> able to fix it in a not too big delay ?
> - screenshots for all modified elements, volunteers ?
> - new and noteworthy section, I can start it
>
>
> We're now 1 year since we released 2.13, I think users are waiting this 3.0
> .
>
> I am as a user
>
>
> Thanks
> On Tuesday, March 15, 2016, Philippe Mouawad 
> wrote:
>
>>
>>
>> On Tue, Mar 15, 2016 at 9:45 PM, Felix Schumacher <
>> felix.schumac...@internetallee.de
>> >
>> wrote:
>>
>>>
>>>
>>> Am 14. März 2016 21:58:50 MEZ, schrieb Philippe Mouawad <
>>> philippe.moua...@gmail.com
>>> >:
>>> >On Monday, March 14, 2016, Felix Schumacher <
>>> >felix.schumac...@internetallee.de
>>> >
>>> wrote:
>>> >
>>> >> Am 14.03.2016 um 21:34 schrieb Philippe Mouawad:
>>> >>
>>> >>> Hello,
>>> >>> All remaining issues before 3.0 are now fixed.
>>> >>>
>>> >> https://issues.apache.org/jira/browse/HTTPCLIENT-1712
>>> >> means that we can't do kerberos with https. Is this a big problem?
>>> >
>>> >
>>> >are we able to workaround in jmeter the issue ?
>>> >If not it would mean we have to wait for a 4.5.3
>>> >
>>> >It does not seem critical for me but I don't know
>>>
>>> We could work around it. We would have to subclass two classes.
>>> SPnegoScheme and its factory.
>>>
>> Let's do that Felix if you think we need to fix it before 3.0.
>>
>>>
>>> The problem is fixed in httpclients trunk, but I don't know when a next
>>> release is planned.
>>>
>>
>> 4.5.2 was just released, I doubt a new one will be released for such a bug
>>
>>
>>>
>>> Felix
>>>
>>> >
>>> >>
>>> >> Felix
>>> >>
>>> >>>
>>> >>> Except for the documentation screenshots everything is ready for a
>>> >>> release.
>>> >>>
>>> >>> When do we launch the release of 3.0 ?
>>> >>>
>>> >>> Regards
>>> >>> Philippe
>>> >>>
>>> >>>
>>> >>> On Fri, Mar 11, 2016 at 8:20 AM, Milamber >> >
>>> >wrote:
>>> >>>
>>> >>>
>>>  On 08/03/2016 23:02, Philippe Mouawad wrote:
>>> 
>>>  @Milamber, do you intend to take into account before 3.0 release
>>> >the
>>> > notes
>>> > from Benoit Wiart:
>>> > -https://bz.apache.org/bugzilla/show_bug.cgi?id=58426
>>> >
>>> > Not before the 3.0.
>>> 
>>> 
>>>  If not, I suggest we close this one and open a new one to complete
>>> >HiDPI
>>> > support in 3.1
>>> >
>>> > That seems a good idea.
>>> 
>>> 
>>>  Milamber
>>> 
>>> 
>>> >>>
>>> >>>
>>> >>
>>>
>>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>
> --
> Cordialement.
> Philippe Mouawad.

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

On Tue, Mar 15, 2016 at 9:45 PM, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:

>
>
> Am 14. März 2016 21:58:50 MEZ, schrieb Philippe Mouawad <
> philippe.moua...@gmail.com>:
> >On Monday, March 14, 2016, Felix Schumacher <
> >felix.schumac...@internetallee.de> wrote:
> >
> >> Am 14.03.2016 um 21:34 schrieb Philippe Mouawad:
> >>
> >>> Hello,
> >>> All remaining issues before 3.0 are now fixed.
> >>>
> >> https://issues.apache.org/jira/browse/HTTPCLIENT-1712
> >> means that we can't do kerberos with https. Is this a big problem?
> >
> >
> >are we able to workaround in jmeter the issue ?
> >If not it would mean we have to wait for a 4.5.3
> >
> >It does not seem critical for me but I don't know
>
> We could work around it. We would have to subclass two classes.
> SPnegoScheme and its factory.
>
Let's do that Felix if you think we need to fix it before 3.0.

>
> The problem is fixed in httpclients trunk, but I don't know when a next
> release is planned.
>

4.5.2 was just released, I doubt a new one will be released for such a bug


>
> Felix
>
> >
> >>
> >> Felix
> >>
> >>>
> >>> Except for the documentation screenshots everything is ready for a
> >>> release.
> >>>
> >>> When do we launch the release of 3.0 ?
> >>>
> >>> Regards
> >>> Philippe
> >>>
> >>>
> >>> On Fri, Mar 11, 2016 at 8:20 AM, Milamber 
> >wrote:
> >>>
> >>>
>  On 08/03/2016 23:02, Philippe Mouawad wrote:
> 
>  @Milamber, do you intend to take into account before 3.0 release
> >the
> > notes
> > from Benoit Wiart:
> > -https://bz.apache.org/bugzilla/show_bug.cgi?id=58426
> >
> > Not before the 3.0.
> 
> 
>  If not, I suggest we close this one and open a new one to complete
> >HiDPI
> > support in 3.1
> >
> > That seems a good idea.
> 
> 
>  Milamber
> 
> 
> >>>
> >>>
> >>
>
>


-- 
Cordialement.
Philippe Mouawad.

Re: Remaining Work before Release of 3.0

[Felix Schumacher]

Am 14. März 2016 21:58:50 MEZ, schrieb Philippe Mouawad 
:
>On Monday, March 14, 2016, Felix Schumacher <
>felix.schumac...@internetallee.de> wrote:
>
>> Am 14.03.2016 um 21:34 schrieb Philippe Mouawad:
>>
>>> Hello,
>>> All remaining issues before 3.0 are now fixed.
>>>
>> https://issues.apache.org/jira/browse/HTTPCLIENT-1712
>> means that we can't do kerberos with https. Is this a big problem?
>
>
>are we able to workaround in jmeter the issue ?
>If not it would mean we have to wait for a 4.5.3
>
>It does not seem critical for me but I don't know

We could work around it. We would have to subclass two classes. SPnegoScheme 
and its factory. 

The problem is fixed in httpclients trunk, but I don't know when a next release 
is planned. 

Felix

>
>>
>> Felix
>>
>>>
>>> Except for the documentation screenshots everything is ready for a
>>> release.
>>>
>>> When do we launch the release of 3.0 ?
>>>
>>> Regards
>>> Philippe
>>>
>>>
>>> On Fri, Mar 11, 2016 at 8:20 AM, Milamber 
>wrote:
>>>
>>>
 On 08/03/2016 23:02, Philippe Mouawad wrote:

 @Milamber, do you intend to take into account before 3.0 release
>the
> notes
> from Benoit Wiart:
> -https://bz.apache.org/bugzilla/show_bug.cgi?id=58426
>
> Not before the 3.0.


 If not, I suggest we close this one and open a new one to complete
>HiDPI
> support in 3.1
>
> That seems a good idea.


 Milamber


>>>
>>>
>>

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

On Mon, Mar 14, 2016 at 10:24 PM, sebb  wrote:

> That's not quite true.
>
> There are some unsolved regressions:
>
> Bug 59173
>


>
> Bug 59147
>

Not a JMeter bug as per Benoit Wiart note

>
> Bug 59107
>
Fixed, I commented

>
>
>
> There's some partially finished enhancements:
>
> Bug 59171
>

Not a lot of work remaining right ?
I answered

>
> Bug 58986
>
This one is closed as you opened Bug 59091

I consider it more of an enhancement that does not really blocks release in
my opinion.



>
>
> On 14 March 2016 at 20:34, Philippe Mouawad 
> wrote:
> > Hello,
> > All remaining issues before 3.0 are now fixed.
> >
> > Except for the documentation screenshots everything is ready for a
> release.
> >
> > When do we launch the release of 3.0 ?
> >
> > Regards
> > Philippe
> >
> >
> > On Fri, Mar 11, 2016 at 8:20 AM, Milamber  wrote:
> >
> >>
> >>
> >> On 08/03/2016 23:02, Philippe Mouawad wrote:
> >>
> >>> @Milamber, do you intend to take into account before 3.0 release the
> notes
> >>> from Benoit Wiart:
> >>> -https://bz.apache.org/bugzilla/show_bug.cgi?id=58426
> >>>
> >>
> >> Not before the 3.0.
> >>
> >>
> >>> If not, I suggest we close this one and open a new one to complete
> HiDPI
> >>> support in 3.1
> >>>
> >>
> >> That seems a good idea.
> >>
> >>
> >> Milamber
> >>
> >
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
>



-- 
Cordialement.
Philippe Mouawad.

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

On Monday, March 14, 2016, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:

> Am 14.03.2016 um 21:34 schrieb Philippe Mouawad:
>
>> Hello,
>> All remaining issues before 3.0 are now fixed.
>>
> https://issues.apache.org/jira/browse/HTTPCLIENT-1712
> means that we can't do kerberos with https. Is this a big problem?


are we able to workaround in jmeter the issue ?
If not it would mean we have to wait for a 4.5.3

It does not seem critical for me but I don't know

>
> Felix
>
>>
>> Except for the documentation screenshots everything is ready for a
>> release.
>>
>> When do we launch the release of 3.0 ?
>>
>> Regards
>> Philippe
>>
>>
>> On Fri, Mar 11, 2016 at 8:20 AM, Milamber  wrote:
>>
>>
>>> On 08/03/2016 23:02, Philippe Mouawad wrote:
>>>
>>> @Milamber, do you intend to take into account before 3.0 release the
 notes
 from Benoit Wiart:
 -https://bz.apache.org/bugzilla/show_bug.cgi?id=58426

 Not before the 3.0.
>>>
>>>
>>> If not, I suggest we close this one and open a new one to complete HiDPI
 support in 3.1

 That seems a good idea.
>>>
>>>
>>> Milamber
>>>
>>>
>>
>>
>

-- 
Cordialement.
Philippe Mouawad.

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

Hello,
All remaining issues before 3.0 are now fixed.

Except for the documentation screenshots everything is ready for a release.

When do we launch the release of 3.0 ?

Regards
Philippe


On Fri, Mar 11, 2016 at 8:20 AM, Milamber  wrote:

>
>
> On 08/03/2016 23:02, Philippe Mouawad wrote:
>
>> @Milamber, do you intend to take into account before 3.0 release the notes
>> from Benoit Wiart:
>> -https://bz.apache.org/bugzilla/show_bug.cgi?id=58426
>>
>
> Not before the 3.0.
>
>
>> If not, I suggest we close this one and open a new one to complete HiDPI
>> support in 3.1
>>
>
> That seems a good idea.
>
>
> Milamber
>



-- 
Cordialement.
Philippe Mouawad.

Re: Remaining Work before Release of 3.0

[Milamber]

On 08/03/2016 23:02, Philippe Mouawad wrote:

@Milamber, do you intend to take into account before 3.0 release the notes
from Benoit Wiart:
-https://bz.apache.org/bugzilla/show_bug.cgi?id=58426


Not before the 3.0.



If not, I suggest we close this one and open a new one to complete HiDPI
support in 3.1


That seems a good idea.


Milamber

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

Hello,
A little update on progress for 3.0:

I will commit tomorrow this one which improves drastically performances of
JMeter when Parallel download is selected (1.65 more throughput for 15
Threads,  it will increase with number of threads)
- https://bz.apache.org/bugzilla/show_bug.cgi?id=52073


A nasty bug (Synchronization issue) was reported today , I think I fixed it
but it would be great if you could review it:
- https://bz.apache.org/bugzilla/show_bug.cgi?id=59146

Felix is waiting feedback on his proposal for:
- https://bz.apache.org/bugzilla/show_bug.cgi?id=59083

I gave mine, I think last patch proposal is OK. If patch is commited this
bug can also be closed: https://bz.apache.org/bugzilla/show_bug.cgi?id=59131

@Milamber, do you intend to take into account before 3.0 release the notes
from Benoit Wiart:
- https://bz.apache.org/bugzilla/show_bug.cgi?id=58426

If not, I suggest we close this one and open a new one to complete HiDPI
support in 3.1

I suggest that we delay the fix of those 2 to next release :
- https://bz.apache.org/bugzilla/show_bug.cgi?id=58807 =>
- https://bz.apache.org/bugzilla/show_bug.cgi?id=56141 => I am waiting for
more information


Do you think we can target a release date ?

Regards

On Mon, Mar 7, 2016 at 10:10 PM, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:

> Am 07.03.2016 um 21:58 schrieb Milamber:
>
>>
>> Oh, second logo (jmeter2.svg) is punchy and great!
>> Perhaps try a version with J and Meter char border with the same color of
>> 'inside' char (no border) (using the inside color as the border too)
>>
>> (and reduce a little the size of TM mark)
>>
> Version with Border color == Inside color and smaller TM.
>
> Felix
>
>
>>
>> On 07/03/2016 20:47, Felix Schumacher wrote:
>>
>>> Am 07.03.2016 um 21:26 schrieb Philippe Mouawad:
>>>
 On Mon, Mar 7, 2016 at 7:59 PM, Felix Schumacher <
 felix.schumac...@internetallee.de> wrote:

 Am 27.02.2016 um 11:06 schrieb Philippe Mouawad:
>
> Hello
>> I had a look at bugs, enhancements and pending mailing lists
>> discussions.
>>
>> After release of HttpClient 4.5.2, we are now ready to finalize the
>> 3.0
>> version.
>>
>> I added a Tag "fix_before_3.0" on issues that are pending :
>>
>> Should we adapt the logo to the new feather?
>
> if you have design skills why not :-) ?

>>> Skill is relative.
>>>
>>> I have attached two versions of an adapted logo.
>>>
>>> Regards,
>>>  Felix
>>>
>>>

 Felix
>
> Here is the list:
>> 59083 JMeter HTTP NEW --- HTTP Request : Make
>> Method
>> field editable so that additional methods (Webdav) can be added
>> easily  =>
>> PATCH nearly ready to be commited
>> 59038 JMeter HTTP NEW --- Deprecate HTTPClient 3.1
>> related elements => Some deprecation work to do
>> 59033 JMeter HTTP NEW --- Parallel Download : Add
>> CSS
>> Parsing to extract links from CSS files => Patch Part1 ready to
>> commit,
>> we could stop for now and complete it in 3.1 by adding an
>> implementation
>> similar to HTMLRegexParser that extracts url()
>> 58986 JMeter Main REOP --- Report/Dashboard reuses the
>> same output directory
>> => Waiting for sebb answer, not a lot of work
>> 58807 JMeter HTTP NEED ---
>> https.use.cached.ssl.context=false is broken
>> => Patch waiting to be commited
>> 57182 JMeter Main NEW --- Better defaults : Save
>> idle
>> time by default
>> => Not mandatory
>>
>>
>> I will work on:
>>
>>  - 59038
>>  - 58986 if you are ok with my solution last comment on bug
>>
>>
>> Besides this we had some documentation update:
>>
>>  - Screenshots
>>  - New and Noteworthy section which should be very rich
>>
>>
>> Once this is done, for release, what do you think of the following:
>>
>>  - We send on user mailing list and twitter a message to ask
>> users to
>>  test nightly build and wait for 1 week for feedback
>>  - We then start the release process
>>
>>
>>
>> Regards
>> Philippe
>>
>>
>>

>>>
>>
>


-- 
Cordialement.
Philippe Mouawad.

Re: New logo for JMeter 3.0 Was: Remaining Work before Release of 3.0

[Philippe Mouawad]

Thanks Felix, very nice work !

On Tue, Mar 8, 2016 at 9:17 PM, Milamber  wrote:

>
> Thanks Felix for your work!
>
> If nobody have more comments or suggestions on color/logo/border/etc, we
> (Felix?) can start a thread vote tomorrow to ask your preference about
> these new logos?
>
>
>
>
>
> On 08/03/2016 19:56, Milamber wrote:
>
>> Ok great, you have read in my mind!
>>
>> On 08/03/2016 19:48, Felix Schumacher wrote:
>>
>>> All variants can be seen on http://home.apache.org/~fschumacher/
>>>
>>> Felix
>>>
>>> Am 08.03.2016 um 20:28 schrieb Felix Schumacher:
>>>
 Am 07.03.2016 um 22:19 schrieb Milamber:

>
> Ok looks seems better smoothly
>
> Can you try with the jmeter2.svg border color was the inside color?
> and TM with the light gray. (just for compare the 3 and next 4)
>
 And now I have filled the TM with the same gray as the hidden TM in the
 feather.

 Felix

>
> Thanks
>
> On 07/03/2016 21:10, Felix Schumacher wrote:
>
>> Am 07.03.2016 um 21:58 schrieb Milamber:
>>
>>>
>>> Oh, second logo (jmeter2.svg) is punchy and great!
>>> Perhaps try a version with J and Meter char border with the same
>>> color of 'inside' char (no border) (using the inside color as the border
>>> too)
>>>
>>> (and reduce a little the size of TM mark)
>>>
>> Version with Border color == Inside color and smaller TM.
>>
>> Felix
>>
>>>
>>>
>>> On 07/03/2016 20:47, Felix Schumacher wrote:
>>>
 Am 07.03.2016 um 21:26 schrieb Philippe Mouawad:

> On Mon, Mar 7, 2016 at 7:59 PM, Felix Schumacher <
> felix.schumac...@internetallee.de> wrote:
>
> Am 27.02.2016 um 11:06 schrieb Philippe Mouawad:
>>
>> Hello
>>> I had a look at bugs, enhancements and pending mailing lists
>>> discussions.
>>>
>>> After release of HttpClient 4.5.2, we are now ready to finalize
>>> the 3.0
>>> version.
>>>
>>> I added a Tag "fix_before_3.0" on issues that are pending :
>>>
>>> Should we adapt the logo to the new feather?
>>
>> if you have design skills why not :-) ?
>
 Skill is relative.

 I have attached two versions of an adapted logo.

 Regards,
  Felix


>
> Felix
>>
>> Here is the list:
>>> 59083 JMeter HTTP NEW --- HTTP Request : Make
>>> Method
>>> field editable so that additional methods (Webdav) can be added
>>> easily  =>
>>> PATCH nearly ready to be commited
>>> 59038 JMeter HTTP NEW --- Deprecate HTTPClient
>>> 3.1
>>> related elements => Some deprecation work to do
>>> 59033 JMeter HTTP NEW --- Parallel Download :
>>> Add CSS
>>> Parsing to extract links from CSS files => Patch Part1 ready to
>>> commit,
>>> we could stop for now and complete it in 3.1 by adding an
>>> implementation
>>> similar to HTMLRegexParser that extracts url()
>>> 58986 JMeter Main REOP --- Report/Dashboard
>>> reuses the
>>> same output directory
>>> => Waiting for sebb answer, not a lot of work
>>> 58807 JMeter HTTP NEED ---
>>> https.use.cached.ssl.context=false is broken
>>> => Patch waiting to be commited
>>> 57182 JMeter Main NEW --- Better defaults : Save
>>> idle
>>> time by default
>>> => Not mandatory
>>>
>>>
>>> I will work on:
>>>
>>>  - 59038
>>>  - 58986 if you are ok with my solution last comment on bug
>>>
>>>
>>> Besides this we had some documentation update:
>>>
>>>  - Screenshots
>>>  - New and Noteworthy section which should be very rich
>>>
>>>
>>> Once this is done, for release, what do you think of the
>>> following:
>>>
>>>  - We send on user mailing list and twitter a message to ask
>>> users to
>>>  test nightly build and wait for 1 week for feedback
>>>  - We then start the release process
>>>
>>>
>>>
>>> Regards
>>> Philippe
>>>
>>>
>>>
>

>>>
>>
>

>>>
>>>
>>
>>
>


-- 
Cordialement.
Philippe Mouawad.

Re: New logo for JMeter 3.0 Was: Remaining Work before Release of 3.0

[Milamber]

Thanks Felix for your work!

If nobody have more comments or suggestions on color/logo/border/etc, we 
(Felix?) can start a thread vote tomorrow to ask your preference about 
these new logos?





On 08/03/2016 19:56, Milamber wrote:

Ok great, you have read in my mind!

On 08/03/2016 19:48, Felix Schumacher wrote:

All variants can be seen on http://home.apache.org/~fschumacher/

Felix

Am 08.03.2016 um 20:28 schrieb Felix Schumacher:

Am 07.03.2016 um 22:19 schrieb Milamber:


Ok looks seems better smoothly

Can you try with the jmeter2.svg border color was the inside color? 
and TM with the light gray. (just for compare the 3 and next 4)
And now I have filled the TM with the same gray as the hidden TM in 
the feather.


Felix


Thanks

On 07/03/2016 21:10, Felix Schumacher wrote:

Am 07.03.2016 um 21:58 schrieb Milamber:


Oh, second logo (jmeter2.svg) is punchy and great!
Perhaps try a version with J and Meter char border with the same 
color of 'inside' char (no border) (using the inside color as the 
border too)


(and reduce a little the size of TM mark)

Version with Border color == Inside color and smaller TM.

Felix



On 07/03/2016 20:47, Felix Schumacher wrote:

Am 07.03.2016 um 21:26 schrieb Philippe Mouawad:

On Mon, Mar 7, 2016 at 7:59 PM, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:


Am 27.02.2016 um 11:06 schrieb Philippe Mouawad:


Hello
I had a look at bugs, enhancements and pending mailing lists 
discussions.


After release of HttpClient 4.5.2, we are now ready to 
finalize the 3.0

version.

I added a Tag "fix_before_3.0" on issues that are pending :


Should we adapt the logo to the new feather?


if you have design skills why not :-) ?

Skill is relative.

I have attached two versions of an adapted logo.

Regards,
 Felix





Felix


Here is the list:
59083 JMeter HTTP NEW --- HTTP Request : Make 
Method
field editable so that additional methods (Webdav) can be 
added easily  =>

PATCH nearly ready to be commited
59038 JMeter HTTP NEW --- Deprecate 
HTTPClient 3.1

related elements => Some deprecation work to do
59033 JMeter HTTP NEW --- Parallel Download : 
Add CSS

Parsing to extract links from CSS files => Patch Part1 ready to
commit,
we could stop for now and complete it in 3.1 by adding an 
implementation

similar to HTMLRegexParser that extracts url()
58986 JMeter Main REOP --- Report/Dashboard 
reuses the

same output directory
=> Waiting for sebb answer, not a lot of work
58807 JMeter HTTP NEED ---
https.use.cached.ssl.context=false is broken
=> Patch waiting to be commited
57182 JMeter Main NEW --- Better defaults : 
Save idle

time by default
=> Not mandatory


I will work on:

 - 59038
 - 58986 if you are ok with my solution last comment on bug


Besides this we had some documentation update:

 - Screenshots
 - New and Noteworthy section which should be very rich


Once this is done, for release, what do you think of the 
following:


 - We send on user mailing list and twitter a message to 
ask users to

 test nightly build and wait for 1 week for feedback
 - We then start the release process



Regards
Philippe

Re: New logo for JMeter 3.0 Was: Remaining Work before Release of 3.0

[Milamber]

Ok great, you have read in my mind!

On 08/03/2016 19:48, Felix Schumacher wrote:

All variants can be seen on http://home.apache.org/~fschumacher/

Felix

Am 08.03.2016 um 20:28 schrieb Felix Schumacher:

Am 07.03.2016 um 22:19 schrieb Milamber:


Ok looks seems better smoothly

Can you try with the jmeter2.svg border color was the inside color? 
and TM with the light gray. (just for compare the 3 and next 4)
And now I have filled the TM with the same gray as the hidden TM in 
the feather.


Felix


Thanks

On 07/03/2016 21:10, Felix Schumacher wrote:

Am 07.03.2016 um 21:58 schrieb Milamber:


Oh, second logo (jmeter2.svg) is punchy and great!
Perhaps try a version with J and Meter char border with the same 
color of 'inside' char (no border) (using the inside color as the 
border too)


(and reduce a little the size of TM mark)

Version with Border color == Inside color and smaller TM.

Felix



On 07/03/2016 20:47, Felix Schumacher wrote:

Am 07.03.2016 um 21:26 schrieb Philippe Mouawad:

On Mon, Mar 7, 2016 at 7:59 PM, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:


Am 27.02.2016 um 11:06 schrieb Philippe Mouawad:


Hello
I had a look at bugs, enhancements and pending mailing lists 
discussions.


After release of HttpClient 4.5.2, we are now ready to 
finalize the 3.0

version.

I added a Tag "fix_before_3.0" on issues that are pending :


Should we adapt the logo to the new feather?


if you have design skills why not :-) ?

Skill is relative.

I have attached two versions of an adapted logo.

Regards,
 Felix





Felix


Here is the list:
59083 JMeter HTTP NEW --- HTTP Request : 
Make Method
field editable so that additional methods (Webdav) can be 
added easily  =>

PATCH nearly ready to be commited
59038 JMeter HTTP NEW --- Deprecate HTTPClient 
3.1

related elements => Some deprecation work to do
59033 JMeter HTTP NEW --- Parallel Download : 
Add CSS
Parsing to extract links from CSS files => Patch Part1 
ready to

commit,
we could stop for now and complete it in 3.1 by adding an 
implementation

similar to HTMLRegexParser that extracts url()
58986 JMeter Main REOP --- Report/Dashboard 
reuses the

same output directory
=> Waiting for sebb answer, not a lot of work
58807 JMeter HTTP NEED ---
https.use.cached.ssl.context=false is broken
=> Patch waiting to be commited
57182 JMeter Main NEW --- Better defaults : 
Save idle

time by default
=> Not mandatory


I will work on:

 - 59038
 - 58986 if you are ok with my solution last comment on bug


Besides this we had some documentation update:

 - Screenshots
 - New and Noteworthy section which should be very rich


Once this is done, for release, what do you think of the 
following:


 - We send on user mailing list and twitter a message to 
ask users to

 test nightly build and wait for 1 week for feedback
 - We then start the release process



Regards
Philippe

Re: New logo for JMeter 3.0 Was: Remaining Work before Release of 3.0

[Milamber]

Ok great, perhaps a last version: the J of JMeter with the Red of APACHE 
and the Meter in black (like jmeter.svg)


I've prepare this page to compare the versions:

http://www.milamberspace.net/logo30/




On 08/03/2016 19:28, Felix Schumacher wrote:

Am 07.03.2016 um 22:19 schrieb Milamber:


Ok looks seems better smoothly

Can you try with the jmeter2.svg border color was the inside color? 
and TM with the light gray. (just for compare the 3 and next 4)
And now I have filled the TM with the same gray as the hidden TM in 
the feather.


Felix


Thanks

On 07/03/2016 21:10, Felix Schumacher wrote:

Am 07.03.2016 um 21:58 schrieb Milamber:


Oh, second logo (jmeter2.svg) is punchy and great!
Perhaps try a version with J and Meter char border with the same 
color of 'inside' char (no border) (using the inside color as the 
border too)


(and reduce a little the size of TM mark)

Version with Border color == Inside color and smaller TM.

Felix



On 07/03/2016 20:47, Felix Schumacher wrote:

Am 07.03.2016 um 21:26 schrieb Philippe Mouawad:

On Mon, Mar 7, 2016 at 7:59 PM, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:


Am 27.02.2016 um 11:06 schrieb Philippe Mouawad:


Hello
I had a look at bugs, enhancements and pending mailing lists 
discussions.


After release of HttpClient 4.5.2, we are now ready to finalize 
the 3.0

version.

I added a Tag "fix_before_3.0" on issues that are pending :


Should we adapt the logo to the new feather?


if you have design skills why not :-) ?

Skill is relative.

I have attached two versions of an adapted logo.

Regards,
 Felix





Felix


Here is the list:
59083 JMeter HTTP NEW --- HTTP Request : 
Make Method
field editable so that additional methods (Webdav) can be added 
easily  =>

PATCH nearly ready to be commited
59038 JMeter HTTP NEW --- Deprecate HTTPClient 3.1
related elements => Some deprecation work to do
59033 JMeter HTTP NEW --- Parallel Download : 
Add CSS
Parsing to extract links from CSS files => Patch Part1 
ready to

commit,
we could stop for now and complete it in 3.1 by adding an 
implementation

similar to HTMLRegexParser that extracts url()
58986 JMeter Main REOP --- Report/Dashboard 
reuses the

same output directory
=> Waiting for sebb answer, not a lot of work
58807 JMeter HTTP NEED ---
https.use.cached.ssl.context=false is broken
=> Patch waiting to be commited
57182 JMeter Main NEW --- Better defaults : 
Save idle

time by default
=> Not mandatory


I will work on:

 - 59038
 - 58986 if you are ok with my solution last comment on bug


Besides this we had some documentation update:

 - Screenshots
 - New and Noteworthy section which should be very rich


Once this is done, for release, what do you think of the 
following:


 - We send on user mailing list and twitter a message to 
ask users to

 test nightly build and wait for 1 week for feedback
 - We then start the release process



Regards
Philippe

Re: New logo for JMeter 3.0 Was: Remaining Work before Release of 3.0

[Felix Schumacher]

All variants can be seen on http://home.apache.org/~fschumacher/

Felix

Am 08.03.2016 um 20:28 schrieb Felix Schumacher:

Am 07.03.2016 um 22:19 schrieb Milamber:


Ok looks seems better smoothly

Can you try with the jmeter2.svg border color was the inside color? 
and TM with the light gray. (just for compare the 3 and next 4)
And now I have filled the TM with the same gray as the hidden TM in 
the feather.


Felix


Thanks

On 07/03/2016 21:10, Felix Schumacher wrote:

Am 07.03.2016 um 21:58 schrieb Milamber:


Oh, second logo (jmeter2.svg) is punchy and great!
Perhaps try a version with J and Meter char border with the same 
color of 'inside' char (no border) (using the inside color as the 
border too)


(and reduce a little the size of TM mark)

Version with Border color == Inside color and smaller TM.

Felix



On 07/03/2016 20:47, Felix Schumacher wrote:

Am 07.03.2016 um 21:26 schrieb Philippe Mouawad:

On Mon, Mar 7, 2016 at 7:59 PM, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:


Am 27.02.2016 um 11:06 schrieb Philippe Mouawad:


Hello
I had a look at bugs, enhancements and pending mailing lists 
discussions.


After release of HttpClient 4.5.2, we are now ready to finalize 
the 3.0

version.

I added a Tag "fix_before_3.0" on issues that are pending :


Should we adapt the logo to the new feather?


if you have design skills why not :-) ?

Skill is relative.

I have attached two versions of an adapted logo.

Regards,
 Felix





Felix


Here is the list:
59083 JMeter HTTP NEW --- HTTP Request : 
Make Method
field editable so that additional methods (Webdav) can be added 
easily  =>

PATCH nearly ready to be commited
59038 JMeter HTTP NEW --- Deprecate HTTPClient 3.1
related elements => Some deprecation work to do
59033 JMeter HTTP NEW --- Parallel Download : 
Add CSS
Parsing to extract links from CSS files => Patch Part1 
ready to

commit,
we could stop for now and complete it in 3.1 by adding an 
implementation

similar to HTMLRegexParser that extracts url()
58986 JMeter Main REOP --- Report/Dashboard 
reuses the

same output directory
=> Waiting for sebb answer, not a lot of work
58807 JMeter HTTP NEED ---
https.use.cached.ssl.context=false is broken
=> Patch waiting to be commited
57182 JMeter Main NEW --- Better defaults : 
Save idle

time by default
=> Not mandatory


I will work on:

 - 59038
 - 58986 if you are ok with my solution last comment on bug


Besides this we had some documentation update:

 - Screenshots
 - New and Noteworthy section which should be very rich


Once this is done, for release, what do you think of the 
following:


 - We send on user mailing list and twitter a message to 
ask users to

 test nightly build and wait for 1 week for feedback
 - We then start the release process



Regards
Philippe

Re: New logo for JMeter 3.0 Was: Remaining Work before Release of 3.0

[Felix Schumacher]

Am 07.03.2016 um 22:19 schrieb Milamber:


Ok looks seems better smoothly

Can you try with the jmeter2.svg border color was the inside color? 
and TM with the light gray. (just for compare the 3 and next 4)
And now I have filled the TM with the same gray as the hidden TM in the 
feather.


Felix


Thanks

On 07/03/2016 21:10, Felix Schumacher wrote:

Am 07.03.2016 um 21:58 schrieb Milamber:


Oh, second logo (jmeter2.svg) is punchy and great!
Perhaps try a version with J and Meter char border with the same 
color of 'inside' char (no border) (using the inside color as the 
border too)


(and reduce a little the size of TM mark)

Version with Border color == Inside color and smaller TM.

Felix



On 07/03/2016 20:47, Felix Schumacher wrote:

Am 07.03.2016 um 21:26 schrieb Philippe Mouawad:

On Mon, Mar 7, 2016 at 7:59 PM, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:


Am 27.02.2016 um 11:06 schrieb Philippe Mouawad:


Hello
I had a look at bugs, enhancements and pending mailing lists 
discussions.


After release of HttpClient 4.5.2, we are now ready to finalize 
the 3.0

version.

I added a Tag "fix_before_3.0" on issues that are pending :


Should we adapt the logo to the new feather?


if you have design skills why not :-) ?

Skill is relative.

I have attached two versions of an adapted logo.

Regards,
 Felix





Felix


Here is the list:
59083 JMeter HTTP NEW --- HTTP Request : 
Make Method
field editable so that additional methods (Webdav) can be added 
easily  =>

PATCH nearly ready to be commited
59038 JMeter HTTP NEW --- Deprecate HTTPClient 3.1
related elements => Some deprecation work to do
59033 JMeter HTTP NEW --- Parallel Download 
: Add CSS

Parsing to extract links from CSS files => Patch Part1 ready to
commit,
we could stop for now and complete it in 3.1 by adding an 
implementation

similar to HTMLRegexParser that extracts url()
58986 JMeter Main REOP --- Report/Dashboard 
reuses the

same output directory
=> Waiting for sebb answer, not a lot of work
58807 JMeter HTTP NEED ---
https.use.cached.ssl.context=false is broken
=> Patch waiting to be commited
57182 JMeter Main NEW --- Better defaults : 
Save idle

time by default
=> Not mandatory


I will work on:

 - 59038
 - 58986 if you are ok with my solution last comment on bug


Besides this we had some documentation update:

 - Screenshots
 - New and Noteworthy section which should be very rich


Once this is done, for release, what do you think of the following:

 - We send on user mailing list and twitter a message to ask 
users to

 test nightly build and wait for 1 week for feedback
 - We then start the release process



Regards
Philippe

Re: New logo for JMeter 3.0 Was: Remaining Work before Release of 3.0

[Felix Schumacher]

Am 07.03.2016 um 22:19 schrieb Milamber:


Ok looks seems better smoothly

Can you try with the jmeter2.svg border color was the inside color? 
and TM with the light gray. (just for compare the 3 and next 4)

I didn't use light gray, but the dark gray of the "meter".

Felix


Thanks

On 07/03/2016 21:10, Felix Schumacher wrote:

Am 07.03.2016 um 21:58 schrieb Milamber:


Oh, second logo (jmeter2.svg) is punchy and great!
Perhaps try a version with J and Meter char border with the same 
color of 'inside' char (no border) (using the inside color as the 
border too)


(and reduce a little the size of TM mark)

Version with Border color == Inside color and smaller TM.

Felix



On 07/03/2016 20:47, Felix Schumacher wrote:

Am 07.03.2016 um 21:26 schrieb Philippe Mouawad:

On Mon, Mar 7, 2016 at 7:59 PM, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:


Am 27.02.2016 um 11:06 schrieb Philippe Mouawad:


Hello
I had a look at bugs, enhancements and pending mailing lists 
discussions.


After release of HttpClient 4.5.2, we are now ready to finalize 
the 3.0

version.

I added a Tag "fix_before_3.0" on issues that are pending :


Should we adapt the logo to the new feather?


if you have design skills why not :-) ?

Skill is relative.

I have attached two versions of an adapted logo.

Regards,
 Felix





Felix


Here is the list:
59083 JMeter HTTP NEW --- HTTP Request : 
Make Method
field editable so that additional methods (Webdav) can be added 
easily  =>

PATCH nearly ready to be commited
59038 JMeter HTTP NEW --- Deprecate HTTPClient 3.1
related elements => Some deprecation work to do
59033 JMeter HTTP NEW --- Parallel Download 
: Add CSS

Parsing to extract links from CSS files => Patch Part1 ready to
commit,
we could stop for now and complete it in 3.1 by adding an 
implementation

similar to HTMLRegexParser that extracts url()
58986 JMeter Main REOP --- Report/Dashboard 
reuses the

same output directory
=> Waiting for sebb answer, not a lot of work
58807 JMeter HTTP NEED ---
https.use.cached.ssl.context=false is broken
=> Patch waiting to be commited
57182 JMeter Main NEW --- Better defaults : 
Save idle

time by default
=> Not mandatory


I will work on:

 - 59038
 - 58986 if you are ok with my solution last comment on bug


Besides this we had some documentation update:

 - Screenshots
 - New and Noteworthy section which should be very rich


Once this is done, for release, what do you think of the following:

 - We send on user mailing list and twitter a message to ask 
users to

 test nightly build and wait for 1 week for feedback
 - We then start the release process



Regards
Philippe

Re: New logo for JMeter 3.0 Was: Remaining Work before Release of 3.0

[Philippe Mouawad]

Hi,
Nice first logos.

My preferences goes for a mix of jmeter.svg (black)  but the TM in red as
in jmeter2.svg

Regards

On Tuesday, March 8, 2016, Vladimir Sitnikov 
wrote:

> >Can you try with the jmeter2.svg border color was the inside color? and
> TM with the light gray. (just for compare the 3 and next 4)
>
> I like jmeter.svg better (the one with just plain black).
>
> Vladimir
>


-- 
Cordialement.
Philippe Mouawad.

Re: New logo for JMeter 3.0 Was: Remaining Work before Release of 3.0

[Vladimir Sitnikov]

>Can you try with the jmeter2.svg border color was the inside color? and TM 
>with the light gray. (just for compare the 3 and next 4)

I like jmeter.svg better (the one with just plain black).

Vladimir

New logo for JMeter 3.0 Was: Remaining Work before Release of 3.0

[Milamber]

Ok looks seems better smoothly

Can you try with the jmeter2.svg border color was the inside color? and 
TM with the light gray. (just for compare the 3 and next 4)


Thanks

On 07/03/2016 21:10, Felix Schumacher wrote:

Am 07.03.2016 um 21:58 schrieb Milamber:


Oh, second logo (jmeter2.svg) is punchy and great!
Perhaps try a version with J and Meter char border with the same 
color of 'inside' char (no border) (using the inside color as the 
border too)


(and reduce a little the size of TM mark)

Version with Border color == Inside color and smaller TM.

Felix



On 07/03/2016 20:47, Felix Schumacher wrote:

Am 07.03.2016 um 21:26 schrieb Philippe Mouawad:

On Mon, Mar 7, 2016 at 7:59 PM, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:


Am 27.02.2016 um 11:06 schrieb Philippe Mouawad:


Hello
I had a look at bugs, enhancements and pending mailing lists 
discussions.


After release of HttpClient 4.5.2, we are now ready to finalize 
the 3.0

version.

I added a Tag "fix_before_3.0" on issues that are pending :


Should we adapt the logo to the new feather?


if you have design skills why not :-) ?

Skill is relative.

I have attached two versions of an adapted logo.

Regards,
 Felix





Felix


Here is the list:
59083 JMeter HTTP NEW --- HTTP Request : Make 
Method
field editable so that additional methods (Webdav) can be added 
easily  =>

PATCH nearly ready to be commited
59038 JMeter HTTP NEW --- Deprecate 
HTTPClient 3.1

related elements => Some deprecation work to do
59033 JMeter HTTP NEW --- Parallel Download : 
Add CSS

Parsing to extract links from CSS files => Patch Part1 ready to
commit,
we could stop for now and complete it in 3.1 by adding an 
implementation

similar to HTMLRegexParser that extracts url()
58986 JMeter Main REOP --- Report/Dashboard 
reuses the

same output directory
=> Waiting for sebb answer, not a lot of work
58807 JMeter HTTP NEED ---
https.use.cached.ssl.context=false is broken
=> Patch waiting to be commited
57182 JMeter Main NEW --- Better defaults : 
Save idle

time by default
=> Not mandatory


I will work on:

 - 59038
 - 58986 if you are ok with my solution last comment on bug


Besides this we had some documentation update:

 - Screenshots
 - New and Noteworthy section which should be very rich


Once this is done, for release, what do you think of the following:

 - We send on user mailing list and twitter a message to ask 
users to

 test nightly build and wait for 1 week for feedback
 - We then start the release process



Regards
Philippe

Re: Remaining Work before Release of 3.0

[Felix Schumacher]

Am 07.03.2016 um 21:58 schrieb Milamber:


Oh, second logo (jmeter2.svg) is punchy and great!
Perhaps try a version with J and Meter char border with the same color 
of 'inside' char (no border) (using the inside color as the border too)


(and reduce a little the size of TM mark)

Version with Border color == Inside color and smaller TM.

Felix



On 07/03/2016 20:47, Felix Schumacher wrote:

Am 07.03.2016 um 21:26 schrieb Philippe Mouawad:

On Mon, Mar 7, 2016 at 7:59 PM, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:


Am 27.02.2016 um 11:06 schrieb Philippe Mouawad:


Hello
I had a look at bugs, enhancements and pending mailing lists 
discussions.


After release of HttpClient 4.5.2, we are now ready to finalize 
the 3.0

version.

I added a Tag "fix_before_3.0" on issues that are pending :


Should we adapt the logo to the new feather?


if you have design skills why not :-) ?

Skill is relative.

I have attached two versions of an adapted logo.

Regards,
 Felix





Felix


Here is the list:
59083 JMeter HTTP NEW --- HTTP Request : Make 
Method
field editable so that additional methods (Webdav) can be added 
easily  =>

PATCH nearly ready to be commited
59038 JMeter HTTP NEW --- Deprecate HTTPClient 
3.1

related elements => Some deprecation work to do
59033 JMeter HTTP NEW --- Parallel Download : 
Add CSS

Parsing to extract links from CSS files => Patch Part1 ready to
commit,
we could stop for now and complete it in 3.1 by adding an 
implementation

similar to HTMLRegexParser that extracts url()
58986 JMeter Main REOP --- Report/Dashboard reuses 
the

same output directory
=> Waiting for sebb answer, not a lot of work
58807 JMeter HTTP NEED ---
https.use.cached.ssl.context=false is broken
=> Patch waiting to be commited
57182 JMeter Main NEW --- Better defaults : 
Save idle

time by default
=> Not mandatory


I will work on:

 - 59038
 - 58986 if you are ok with my solution last comment on bug


Besides this we had some documentation update:

 - Screenshots
 - New and Noteworthy section which should be very rich


Once this is done, for release, what do you think of the following:

 - We send on user mailing list and twitter a message to ask 
users to

 test nightly build and wait for 1 week for feedback
 - We then start the release process



Regards
Philippe

Re: Remaining Work before Release of 3.0

[Milamber]

Oh, second logo (jmeter2.svg) is punchy and great!
Perhaps try a version with J and Meter char border with the same color 
of 'inside' char (no border) (using the inside color as the border too)


(and reduce a little the size of TM mark)


On 07/03/2016 20:47, Felix Schumacher wrote:

Am 07.03.2016 um 21:26 schrieb Philippe Mouawad:

On Mon, Mar 7, 2016 at 7:59 PM, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:


Am 27.02.2016 um 11:06 schrieb Philippe Mouawad:


Hello
I had a look at bugs, enhancements and pending mailing lists 
discussions.


After release of HttpClient 4.5.2, we are now ready to finalize the 
3.0

version.

I added a Tag "fix_before_3.0" on issues that are pending :


Should we adapt the logo to the new feather?


if you have design skills why not :-) ?

Skill is relative.

I have attached two versions of an adapted logo.

Regards,
 Felix





Felix


Here is the list:
59083 JMeter HTTP NEW --- HTTP Request : Make 
Method
field editable so that additional methods (Webdav) can be added 
easily  =>

PATCH nearly ready to be commited
59038 JMeter HTTP NEW --- Deprecate HTTPClient 3.1
related elements => Some deprecation work to do
59033 JMeter HTTP NEW --- Parallel Download : 
Add CSS

Parsing to extract links from CSS files => Patch Part1 ready to
commit,
we could stop for now and complete it in 3.1 by adding an 
implementation

similar to HTMLRegexParser that extracts url()
58986 JMeter Main REOP --- Report/Dashboard reuses the
same output directory
=> Waiting for sebb answer, not a lot of work
58807 JMeter HTTP NEED ---
https.use.cached.ssl.context=false is broken
=> Patch waiting to be commited
57182 JMeter Main NEW --- Better defaults : 
Save idle

time by default
=> Not mandatory


I will work on:

 - 59038
 - 58986 if you are ok with my solution last comment on bug


Besides this we had some documentation update:

 - Screenshots
 - New and Noteworthy section which should be very rich


Once this is done, for release, what do you think of the following:

 - We send on user mailing list and twitter a message to ask 
users to

 test nightly build and wait for 1 week for feedback
 - We then start the release process



Regards
Philippe

Re: Remaining Work before Release of 3.0

[Felix Schumacher]

Am 07.03.2016 um 21:26 schrieb Philippe Mouawad:

On Mon, Mar 7, 2016 at 7:59 PM, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:


Am 27.02.2016 um 11:06 schrieb Philippe Mouawad:


Hello
I had a look at bugs, enhancements and pending mailing lists discussions.

After release of HttpClient 4.5.2, we are now ready to finalize the 3.0
version.

I added a Tag "fix_before_3.0" on issues that are pending :


Should we adapt the logo to the new feather?


if you have design skills why not :-) ?

Skill is relative.

I have attached two versions of an adapted logo.

Regards,
 Felix





Felix


Here is the list:
59083 JMeter HTTP NEW --- HTTP Request : Make Method
field editable so that additional methods (Webdav) can be added easily  =>
PATCH nearly ready to be commited
59038 JMeter HTTP NEW --- Deprecate HTTPClient 3.1
related elements => Some deprecation work to do
59033 JMeter HTTP NEW --- Parallel Download : Add CSS
Parsing to extract links from CSS files => Patch Part1 ready to
commit,
we could stop for now and complete it in 3.1 by adding an implementation
similar to HTMLRegexParser that extracts url()
58986 JMeter Main REOP --- Report/Dashboard reuses the
same output directory
=> Waiting for sebb answer, not a lot of work
58807 JMeter HTTP NEED ---
https.use.cached.ssl.context=false is broken
=> Patch waiting to be commited
57182 JMeter Main NEW --- Better defaults : Save idle
time by default
=> Not mandatory


I will work on:

 - 59038
 - 58986 if you are ok with my solution last comment on bug


Besides this we had some documentation update:

 - Screenshots
 - New and Noteworthy section which should be very rich


Once this is done, for release, what do you think of the following:

 - We send on user mailing list and twitter a message to ask users to
 test nightly build and wait for 1 week for feedback
 - We then start the release process



Regards
Philippe

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

On Mon, Mar 7, 2016 at 7:59 PM, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:

> Am 27.02.2016 um 11:06 schrieb Philippe Mouawad:
>
>> Hello
>> I had a look at bugs, enhancements and pending mailing lists discussions.
>>
>> After release of HttpClient 4.5.2, we are now ready to finalize the 3.0
>> version.
>>
>> I added a Tag "fix_before_3.0" on issues that are pending :
>>
> Should we adapt the logo to the new feather?
>

if you have design skills why not :-) ?


>
> Felix
>
>>
>> Here is the list:
>> 59083 JMeter HTTP NEW --- HTTP Request : Make Method
>> field editable so that additional methods (Webdav) can be added easily  =>
>> PATCH nearly ready to be commited
>> 59038 JMeter HTTP NEW --- Deprecate HTTPClient 3.1
>> related elements => Some deprecation work to do
>> 59033 JMeter HTTP NEW --- Parallel Download : Add CSS
>> Parsing to extract links from CSS files => Patch Part1 ready to
>> commit,
>> we could stop for now and complete it in 3.1 by adding an implementation
>> similar to HTMLRegexParser that extracts url()
>> 58986 JMeter Main REOP --- Report/Dashboard reuses the
>> same output directory
>> => Waiting for sebb answer, not a lot of work
>> 58807 JMeter HTTP NEED ---
>> https.use.cached.ssl.context=false is broken
>> => Patch waiting to be commited
>> 57182 JMeter Main NEW --- Better defaults : Save idle
>> time by default
>> => Not mandatory
>>
>>
>> I will work on:
>>
>> - 59038
>> - 58986 if you are ok with my solution last comment on bug
>>
>>
>> Besides this we had some documentation update:
>>
>> - Screenshots
>> - New and Noteworthy section which should be very rich
>>
>>
>> Once this is done, for release, what do you think of the following:
>>
>> - We send on user mailing list and twitter a message to ask users to
>> test nightly build and wait for 1 week for feedback
>> - We then start the release process
>>
>>
>>
>> Regards
>> Philippe
>>
>>
>


-- 
Cordialement.
Philippe Mouawad.

Re: Remaining Work before Release of 3.0

[Felix Schumacher]

Am 27.02.2016 um 11:06 schrieb Philippe Mouawad:

Hello
I had a look at bugs, enhancements and pending mailing lists discussions.

After release of HttpClient 4.5.2, we are now ready to finalize the 3.0
version.

I added a Tag "fix_before_3.0" on issues that are pending :

Should we adapt the logo to the new feather?

Felix


Here is the list:
59083 JMeter HTTP NEW --- HTTP Request : Make Method
field editable so that additional methods (Webdav) can be added easily  =>
PATCH nearly ready to be commited
59038 JMeter HTTP NEW --- Deprecate HTTPClient 3.1
related elements => Some deprecation work to do
59033 JMeter HTTP NEW --- Parallel Download : Add CSS
Parsing to extract links from CSS files => Patch Part1 ready to commit,
we could stop for now and complete it in 3.1 by adding an implementation
similar to HTMLRegexParser that extracts url()
58986 JMeter Main REOP --- Report/Dashboard reuses the
same output directory
=> Waiting for sebb answer, not a lot of work
58807 JMeter HTTP NEED ---
https.use.cached.ssl.context=false is broken
=> Patch waiting to be commited
57182 JMeter Main NEW --- Better defaults : Save idle
time by default
=> Not mandatory


I will work on:

- 59038
- 58986 if you are ok with my solution last comment on bug


Besides this we had some documentation update:

- Screenshots
- New and Noteworthy section which should be very rich


Once this is done, for release, what do you think of the following:

- We send on user mailing list and twitter a message to ask users to
test nightly build and wait for 1 week for feedback
- We then start the release process



Regards
Philippe

Re: Remaining Work before Release of 3.0

[Andrey Pokhilko]

FYI: I have a regression in trunk:
https://bz.apache.org/bugzilla/show_bug.cgi?id=59133

Andrey Pokhilko

On 02/27/2016 01:06 PM, Philippe Mouawad wrote:
> Hello
> I had a look at bugs, enhancements and pending mailing lists discussions.
>
> After release of HttpClient 4.5.2, we are now ready to finalize the 3.0
> version.
>
> I added a Tag "fix_before_3.0" on issues that are pending :
>
> Here is the list:
> 59083 JMeter HTTP NEW --- HTTP Request : Make Method
> field editable so that additional methods (Webdav) can be added easily  =>
> PATCH nearly ready to be commited
> 59038 JMeter HTTP NEW --- Deprecate HTTPClient 3.1
> related elements => Some deprecation work to do
> 59033 JMeter HTTP NEW --- Parallel Download : Add CSS
> Parsing to extract links from CSS files => Patch Part1 ready to commit,
> we could stop for now and complete it in 3.1 by adding an implementation
> similar to HTMLRegexParser that extracts url()
> 58986 JMeter Main REOP --- Report/Dashboard reuses the
> same output directory
> => Waiting for sebb answer, not a lot of work
> 58807 JMeter HTTP NEED ---
> https.use.cached.ssl.context=false is broken
> => Patch waiting to be commited
> 57182 JMeter Main NEW --- Better defaults : Save idle
> time by default
> => Not mandatory
>
>
> I will work on:
>
>- 59038
>- 58986 if you are ok with my solution last comment on bug
>
>
> Besides this we had some documentation update:
>
>- Screenshots
>- New and Noteworthy section which should be very rich
>
>
> Once this is done, for release, what do you think of the following:
>
>- We send on user mailing list and twitter a message to ask users to
>test nightly build and wait for 1 week for feedback
>- We then start the release process
>
>
>
> Regards
> Philippe
>

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

Hi

On Sat, Mar 5, 2016 at 9:43 AM, Mark Collin 
wrote:

>
> > If Mark is ok with this, what about having a separate sister project of
> > jmeter for the maven plugin (maybe also the jenkins one if we have some
> > volunteers)
> > It could be (if incubated and agreed upon) under the Apache umbrella and
> we
> > could(those who want) participate to it.
> >
> > The release process would be partly dependant on jmeter but as sebb wrote
> > also on maven /jenkins.
> >
>
>
> Not sure I understand what you are proposing here?  A sister version of
> Jmeter using Maven as a build tool?

No

> That seems like an awful lot of work for very little gain.
>
Yes

>
> Or are you suggesting moving the maven-plugin under the Apache umbrella?
>
Yes that was my proposal.



-- 
Cordialement.
Philippe Mouawad.

Re: Remaining Work before Release of 3.0

[Mark Collin]

> If Mark is ok with this, what about having a separate sister project of
> jmeter for the maven plugin (maybe also the jenkins one if we have some
> volunteers)
> It could be (if incubated and agreed upon) under the Apache umbrella and we
> could(those who want) participate to it.
> 
> The release process would be partly dependant on jmeter but as sebb wrote
> also on maven /jenkins.
> 


Not sure I understand what you are proposing here?  A sister version of Jmeter 
using Maven as a build tool?  That seems like an awful lot of work for very 
little gain.

Or are you suggesting moving the maven-plugin under the Apache umbrella?

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

@Mark,
A short term option would be to invite those who wants from JMeter team to
have admin rights on the github repository so that your project has a
bigger community.

I personally would be interested, I do not promise to be an important
contributor but I'll do my best.


Regards

On Friday, March 4, 2016, Philippe Mouawad 
wrote:

>
>
> On Friday, March 4, 2016, sebb  > wrote:
>
>> On 4 March 2016 at 10:38, Mark Collin 
>> wrote:
>> > If the JMeter devs want to put it in core I have no issue with that,
>> however the plugin is a maven project an I don’t think maven projects are
>> wanted in JMeter core :)
>>
>> JMeter does not use Maven as its build tool.
>> It would be a major effort to convert to Maven, so it's not going to
>> be done just in order to support a Maven plugin.
>> If indeed it is ever done (but that is another discussion).
>>
>> However the plugin clearly does not have to be part of the same source
>> tree / build process as JMeter (it's not currently).
>> I think it is better for it to have an entirely separate release
>> process, as it is not only affected by the JMeter version.
>> It's going to be far more dependent on Maven changes.
>>
>> Whether or not it is sensible for the JMeter project to own / maintain
>> the code is another matter.
>> I think not, because JMeter is usable with lots of other build / test
>> tools, and is usable stand-alone.
>>
>> It does not make sense for the JMeter project to maintain plugins for
>> all the possible tools.
>> If we take on a Maven plugin, then how about Groovy, Jenkins,
>> Buildbot, Gradle etc?
>> This does not scale. Furthermore, the code most needs Maven developer
>> expertise, not JMeter expertise.
>
>
>
> If Mark is ok with this, what about having a separate sister project of
> jmeter for the maven plugin (maybe also the jenkins one if we have some
> volunteers)
> It could be (if incubated and agreed upon) under the Apache umbrella and
> we could(those who want) participate to it.
>
> The release process would be partly dependant on jmeter but as sebb wrote
> also on maven /jenkins.
>
>
>
>
>
>>
>> > The website is down at the moment, it’s in the process of being moved
>> over to github.io. (I should probably update the README to note that)
>> >
>> >> On 4 Mar 2016, at 09:51, Antonio Gomes Rodrigues 
>> wrote:
>> >>
>> >> Hi Mark,
>> >>
>> >> I don't have problem with JMeter-Maven-Plugin (and your documentation
>> >> rocks) in particularity
>> >>
>> >> It's only my experience with third party plugin in general and project
>> with
>> >> only one developer.
>> >> And this experience is not always good and it's why I don't like to
>> advise
>> >> my customer to use these projects/plugins
>> >>
>> >> One question, why don't integrate officially your plugin to JMeter
>> core?
>> >>
>> >> About your website, I have a timeout :-(
>> >>
>> >> Thanks to your feedback
>> >>
>> >> Antonio
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
>> >> www.avast.com
>> >> <
>> https://www.avast.com/fr-fr/lp-esg-win-01a?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=OA-2109-C
>> >
>> >> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>> >>
>> >> 2016-03-04 9:29 GMT+01:00 Mark Collin :
>> >>
>> >>>
>> >> Lack of official feature (JMeter plugin, Maven plugin, etc.)
>> >
>> >
>> > non official maven plugin exists and works rather nicely.
>> > What do you mean by JMeter plugin ?
>> >
>> 
>>  In general I have very bad experience with:
>>  third party plugin (not well integrate, not well tested, not up to
>> date
>>  with the latest release, etc.)
>>  Plugin maintained by only one person (less motivation by the
>> developer,
>>  etc.)
>> >>>
>> >>> Bug fixes for the maven plugin are happily accepted.  Also please add
>> >>> issues for things that are:
>> >>> Not well integrated
>> >>> Not well tested
>> >>> Not up to date
>> >>> So that we can fix them (
>> >>> https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues).
>> >>>
>> >>> In regards to it being up to date:
>> >>> The plugin didn’t support JMeter 2.12 Because there were transitive
>> >>> dependency issues with the 2.12 maven release.
>> >>> There were also transitive dependency issues with the JMeter 2.13
>> release
>> >>> that we tried to work around.  Version 1.10.1 of the plugin does use
>> JMeter
>> >>> 2.13.
>> >>> Is there something else we have missed which makes you say it’s not
>> up to
>> >>> date (Feedback is the only way we can make it better)?
>> >>>
>> >>> We are planning a version 2.0.0 of the plugin to coincide with a 3.0
>> >>> JMeter release.  The 2.0.0-SNAPSHOT is available in the Sonatype
>> snapshots
>> >>> repository if you want to try it out and provide some 

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

On Friday, March 4, 2016, sebb  wrote:

> On 4 March 2016 at 10:38, Mark Collin  > wrote:
> > If the JMeter devs want to put it in core I have no issue with that,
> however the plugin is a maven project an I don’t think maven projects are
> wanted in JMeter core :)
>
> JMeter does not use Maven as its build tool.
> It would be a major effort to convert to Maven, so it's not going to
> be done just in order to support a Maven plugin.
> If indeed it is ever done (but that is another discussion).
>
> However the plugin clearly does not have to be part of the same source
> tree / build process as JMeter (it's not currently).
> I think it is better for it to have an entirely separate release
> process, as it is not only affected by the JMeter version.
> It's going to be far more dependent on Maven changes.
>
> Whether or not it is sensible for the JMeter project to own / maintain
> the code is another matter.
> I think not, because JMeter is usable with lots of other build / test
> tools, and is usable stand-alone.
>
> It does not make sense for the JMeter project to maintain plugins for
> all the possible tools.
> If we take on a Maven plugin, then how about Groovy, Jenkins,
> Buildbot, Gradle etc?
> This does not scale. Furthermore, the code most needs Maven developer
> expertise, not JMeter expertise.



If Mark is ok with this, what about having a separate sister project of
jmeter for the maven plugin (maybe also the jenkins one if we have some
volunteers)
It could be (if incubated and agreed upon) under the Apache umbrella and we
could(those who want) participate to it.

The release process would be partly dependant on jmeter but as sebb wrote
also on maven /jenkins.





>
> > The website is down at the moment, it’s in the process of being moved
> over to github.io. (I should probably update the README to note that)
> >
> >> On 4 Mar 2016, at 09:51, Antonio Gomes Rodrigues  > wrote:
> >>
> >> Hi Mark,
> >>
> >> I don't have problem with JMeter-Maven-Plugin (and your documentation
> >> rocks) in particularity
> >>
> >> It's only my experience with third party plugin in general and project
> with
> >> only one developer.
> >> And this experience is not always good and it's why I don't like to
> advise
> >> my customer to use these projects/plugins
> >>
> >> One question, why don't integrate officially your plugin to JMeter core?
> >>
> >> About your website, I have a timeout :-(
> >>
> >> Thanks to your feedback
> >>
> >> Antonio
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
> >> www.avast.com
> >> <
> https://www.avast.com/fr-fr/lp-esg-win-01a?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=OA-2109-C
> >
> >> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >>
> >> 2016-03-04 9:29 GMT+01:00 Mark Collin  >:
> >>
> >>>
> >> Lack of official feature (JMeter plugin, Maven plugin, etc.)
> >
> >
> > non official maven plugin exists and works rather nicely.
> > What do you mean by JMeter plugin ?
> >
> 
>  In general I have very bad experience with:
>  third party plugin (not well integrate, not well tested, not up to
> date
>  with the latest release, etc.)
>  Plugin maintained by only one person (less motivation by the
> developer,
>  etc.)
> >>>
> >>> Bug fixes for the maven plugin are happily accepted.  Also please add
> >>> issues for things that are:
> >>> Not well integrated
> >>> Not well tested
> >>> Not up to date
> >>> So that we can fix them (
> >>> https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues).
> >>>
> >>> In regards to it being up to date:
> >>> The plugin didn’t support JMeter 2.12 Because there were transitive
> >>> dependency issues with the 2.12 maven release.
> >>> There were also transitive dependency issues with the JMeter 2.13
> release
> >>> that we tried to work around.  Version 1.10.1 of the plugin does use
> JMeter
> >>> 2.13.
> >>> Is there something else we have missed which makes you say it’s not up
> to
> >>> date (Feedback is the only way we can make it better)?
> >>>
> >>> We are planning a version 2.0.0 of the plugin to coincide with a 3.0
> >>> JMeter release.  The 2.0.0-SNAPSHOT is available in the Sonatype
> snapshots
> >>> repository if you want to try it out and provide some feedback so that
> we
> >>> can make it better that would be really useful.
> >
>


-- 
Cordialement.
Philippe Mouawad.

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

Hi Mark,
I confirm your project is up to date and very well documented and the work
you're doing is great,
Thanks !

As you know the 3.0 is close to a release, it would be great if you could
confirm that dependencies management is ok this time.

If you could do that when we start the release process it would be even
better.

Regards


On Friday, March 4, 2016, Mark Collin  wrote:

>
> >>> Lack of official feature (JMeter plugin, Maven plugin, etc.)
> >>
> >>
> >> non official maven plugin exists and works rather nicely.
> >> What do you mean by JMeter plugin ?
> >>
> >
> > In general I have very bad experience with:
> > third party plugin (not well integrate, not well tested, not up to date
> > with the latest release, etc.)
> > Plugin maintained by only one person (less motivation by the developer,
> > etc.)
>
> Bug fixes for the maven plugin are happily accepted.  Also please add
> issues for things that are:
> Not well integrated
> Not well tested
> Not up to date
> So that we can fix them (
> https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues).
>
> In regards to it being up to date:
> The plugin didn’t support JMeter 2.12 Because there were transitive
> dependency issues with the 2.12 maven release.
> There were also transitive dependency issues with the JMeter 2.13 release
> that we tried to work around.  Version 1.10.1 of the plugin does use JMeter
> 2.13.
> Is there something else we have missed which makes you say it’s not up to
> date (Feedback is the only way we can make it better)?
>
> We are planning a version 2.0.0 of the plugin to coincide with a 3.0
> JMeter release.  The 2.0.0-SNAPSHOT is available in the Sonatype snapshots
> repository if you want to try it out and provide some feedback so that we
> can make it better that would be really useful.



-- 
Cordialement.
Philippe Mouawad.

Re: Remaining Work before Release of 3.0

[sebb]

On 4 March 2016 at 10:38, Mark Collin  wrote:
> If the JMeter devs want to put it in core I have no issue with that, however 
> the plugin is a maven project an I don’t think maven projects are wanted in 
> JMeter core :)

JMeter does not use Maven as its build tool.
It would be a major effort to convert to Maven, so it's not going to
be done just in order to support a Maven plugin.
If indeed it is ever done (but that is another discussion).

However the plugin clearly does not have to be part of the same source
tree / build process as JMeter (it's not currently).
I think it is better for it to have an entirely separate release
process, as it is not only affected by the JMeter version.
It's going to be far more dependent on Maven changes.

Whether or not it is sensible for the JMeter project to own / maintain
the code is another matter.
I think not, because JMeter is usable with lots of other build / test
tools, and is usable stand-alone.

It does not make sense for the JMeter project to maintain plugins for
all the possible tools.
If we take on a Maven plugin, then how about Groovy, Jenkins,
Buildbot, Gradle etc?
This does not scale. Furthermore, the code most needs Maven developer
expertise, not JMeter expertise.

> The website is down at the moment, it’s in the process of being moved over to 
> github.io. (I should probably update the README to note that)
>
>> On 4 Mar 2016, at 09:51, Antonio Gomes Rodrigues  wrote:
>>
>> Hi Mark,
>>
>> I don't have problem with JMeter-Maven-Plugin (and your documentation
>> rocks) in particularity
>>
>> It's only my experience with third party plugin in general and project with
>> only one developer.
>> And this experience is not always good and it's why I don't like to advise
>> my customer to use these projects/plugins
>>
>> One question, why don't integrate officially your plugin to JMeter core?
>>
>> About your website, I have a timeout :-(
>>
>> Thanks to your feedback
>>
>> Antonio
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
>> www.avast.com
>> 
>> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>> 2016-03-04 9:29 GMT+01:00 Mark Collin :
>>
>>>
>> Lack of official feature (JMeter plugin, Maven plugin, etc.)
>
>
> non official maven plugin exists and works rather nicely.
> What do you mean by JMeter plugin ?
>

 In general I have very bad experience with:
 third party plugin (not well integrate, not well tested, not up to date
 with the latest release, etc.)
 Plugin maintained by only one person (less motivation by the developer,
 etc.)
>>>
>>> Bug fixes for the maven plugin are happily accepted.  Also please add
>>> issues for things that are:
>>> Not well integrated
>>> Not well tested
>>> Not up to date
>>> So that we can fix them (
>>> https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues).
>>>
>>> In regards to it being up to date:
>>> The plugin didn’t support JMeter 2.12 Because there were transitive
>>> dependency issues with the 2.12 maven release.
>>> There were also transitive dependency issues with the JMeter 2.13 release
>>> that we tried to work around.  Version 1.10.1 of the plugin does use JMeter
>>> 2.13.
>>> Is there something else we have missed which makes you say it’s not up to
>>> date (Feedback is the only way we can make it better)?
>>>
>>> We are planning a version 2.0.0 of the plugin to coincide with a 3.0
>>> JMeter release.  The 2.0.0-SNAPSHOT is available in the Sonatype snapshots
>>> repository if you want to try it out and provide some feedback so that we
>>> can make it better that would be really useful.
>

Re: Remaining Work before Release of 3.0

[Antonio Gomes Rodrigues]

Hi,

Anybody know if it's possible to add it?

If no, why?

Thank
Antonio

2016-03-04 11:38 GMT+01:00 Mark Collin :

> If the JMeter devs want to put it in core I have no issue with that,
> however the plugin is a maven project an I don’t think maven projects are
> wanted in JMeter core :)
>
> The website is down at the moment, it’s in the process of being moved over
> to github.io. (I should probably update the README to note that)
>
> > On 4 Mar 2016, at 09:51, Antonio Gomes Rodrigues 
> wrote:
> >
> > Hi Mark,
> >
> > I don't have problem with JMeter-Maven-Plugin (and your documentation
> > rocks) in particularity
> >
> > It's only my experience with third party plugin in general and project
> with
> > only one developer.
> > And this experience is not always good and it's why I don't like to
> advise
> > my customer to use these projects/plugins
> >
> > One question, why don't integrate officially your plugin to JMeter core?
> >
> > About your website, I have a timeout :-(
> >
> > Thanks to your feedback
> >
> > Antonio
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
> > www.avast.com
> > <
> https://www.avast.com/fr-fr/lp-esg-win-01a?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=OA-2109-C
> >
> > <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >
> > 2016-03-04 9:29 GMT+01:00 Mark Collin :
> >
> >>
> > Lack of official feature (JMeter plugin, Maven plugin, etc.)
> 
> 
>  non official maven plugin exists and works rather nicely.
>  What do you mean by JMeter plugin ?
> 
> >>>
> >>> In general I have very bad experience with:
> >>> third party plugin (not well integrate, not well tested, not up to date
> >>> with the latest release, etc.)
> >>> Plugin maintained by only one person (less motivation by the developer,
> >>> etc.)
> >>
> >> Bug fixes for the maven plugin are happily accepted.  Also please add
> >> issues for things that are:
> >> Not well integrated
> >> Not well tested
> >> Not up to date
> >> So that we can fix them (
> >> https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues).
> >>
> >> In regards to it being up to date:
> >> The plugin didn’t support JMeter 2.12 Because there were transitive
> >> dependency issues with the 2.12 maven release.
> >> There were also transitive dependency issues with the JMeter 2.13
> release
> >> that we tried to work around.  Version 1.10.1 of the plugin does use
> JMeter
> >> 2.13.
> >> Is there something else we have missed which makes you say it’s not up
> to
> >> date (Feedback is the only way we can make it better)?
> >>
> >> We are planning a version 2.0.0 of the plugin to coincide with a 3.0
> >> JMeter release.  The 2.0.0-SNAPSHOT is available in the Sonatype
> snapshots
> >> repository if you want to try it out and provide some feedback so that
> we
> >> can make it better that would be really useful.
>
>

Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
www.avast.com

<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Re: Remaining Work before Release of 3.0

[Mark Collin]

If the JMeter devs want to put it in core I have no issue with that, however 
the plugin is a maven project an I don’t think maven projects are wanted in 
JMeter core :)

The website is down at the moment, it’s in the process of being moved over to 
github.io. (I should probably update the README to note that)

> On 4 Mar 2016, at 09:51, Antonio Gomes Rodrigues  wrote:
> 
> Hi Mark,
> 
> I don't have problem with JMeter-Maven-Plugin (and your documentation
> rocks) in particularity
> 
> It's only my experience with third party plugin in general and project with
> only one developer.
> And this experience is not always good and it's why I don't like to advise
> my customer to use these projects/plugins
> 
> One question, why don't integrate officially your plugin to JMeter core?
> 
> About your website, I have a timeout :-(
> 
> Thanks to your feedback
> 
> Antonio
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
> www.avast.com
> 
> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> 
> 2016-03-04 9:29 GMT+01:00 Mark Collin :
> 
>> 
> Lack of official feature (JMeter plugin, Maven plugin, etc.)
 
 
 non official maven plugin exists and works rather nicely.
 What do you mean by JMeter plugin ?
 
>>> 
>>> In general I have very bad experience with:
>>> third party plugin (not well integrate, not well tested, not up to date
>>> with the latest release, etc.)
>>> Plugin maintained by only one person (less motivation by the developer,
>>> etc.)
>> 
>> Bug fixes for the maven plugin are happily accepted.  Also please add
>> issues for things that are:
>> Not well integrated
>> Not well tested
>> Not up to date
>> So that we can fix them (
>> https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues).
>> 
>> In regards to it being up to date:
>> The plugin didn’t support JMeter 2.12 Because there were transitive
>> dependency issues with the 2.12 maven release.
>> There were also transitive dependency issues with the JMeter 2.13 release
>> that we tried to work around.  Version 1.10.1 of the plugin does use JMeter
>> 2.13.
>> Is there something else we have missed which makes you say it’s not up to
>> date (Feedback is the only way we can make it better)?
>> 
>> We are planning a version 2.0.0 of the plugin to coincide with a 3.0
>> JMeter release.  The 2.0.0-SNAPSHOT is available in the Sonatype snapshots
>> repository if you want to try it out and provide some feedback so that we
>> can make it better that would be really useful.

Re: Remaining Work before Release of 3.0

[Antonio Gomes Rodrigues]

Hi Mark,

I don't have problem with JMeter-Maven-Plugin (and your documentation
rocks) in particularity

It's only my experience with third party plugin in general and project with
only one developer.
And this experience is not always good and it's why I don't like to advise
my customer to use these projects/plugins

One question, why don't integrate officially your plugin to JMeter core?

About your website, I have a timeout :-(

Thanks to your feedback

Antonio









Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
www.avast.com

<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2016-03-04 9:29 GMT+01:00 Mark Collin :

>
> >>> Lack of official feature (JMeter plugin, Maven plugin, etc.)
> >>
> >>
> >> non official maven plugin exists and works rather nicely.
> >> What do you mean by JMeter plugin ?
> >>
> >
> > In general I have very bad experience with:
> > third party plugin (not well integrate, not well tested, not up to date
> > with the latest release, etc.)
> > Plugin maintained by only one person (less motivation by the developer,
> > etc.)
>
> Bug fixes for the maven plugin are happily accepted.  Also please add
> issues for things that are:
> Not well integrated
> Not well tested
> Not up to date
> So that we can fix them (
> https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues).
>
> In regards to it being up to date:
> The plugin didn’t support JMeter 2.12 Because there were transitive
> dependency issues with the 2.12 maven release.
> There were also transitive dependency issues with the JMeter 2.13 release
> that we tried to work around.  Version 1.10.1 of the plugin does use JMeter
> 2.13.
> Is there something else we have missed which makes you say it’s not up to
> date (Feedback is the only way we can make it better)?
>
> We are planning a version 2.0.0 of the plugin to coincide with a 3.0
> JMeter release.  The 2.0.0-SNAPSHOT is available in the Sonatype snapshots
> repository if you want to try it out and provide some feedback so that we
> can make it better that would be really useful.

Re: Remaining Work before Release of 3.0

[Mark Collin]

>>> Lack of official feature (JMeter plugin, Maven plugin, etc.)
>> 
>> 
>> non official maven plugin exists and works rather nicely.
>> What do you mean by JMeter plugin ?
>> 
> 
> In general I have very bad experience with:
> third party plugin (not well integrate, not well tested, not up to date
> with the latest release, etc.)
> Plugin maintained by only one person (less motivation by the developer,
> etc.)

Bug fixes for the maven plugin are happily accepted.  Also please add issues 
for things that are:
Not well integrated
Not well tested
Not up to date
So that we can fix them 
(https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues).

In regards to it being up to date:
The plugin didn’t support JMeter 2.12 Because there were transitive dependency 
issues with the 2.12 maven release.
There were also transitive dependency issues with the JMeter 2.13 release that 
we tried to work around.  Version 1.10.1 of the plugin does use JMeter 2.13.
Is there something else we have missed which makes you say it’s not up to date 
(Feedback is the only way we can make it better)?

We are planning a version 2.0.0 of the plugin to coincide with a 3.0 JMeter 
release.  The 2.0.0-SNAPSHOT is available in the Sonatype snapshots repository 
if you want to try it out and provide some feedback so that we can make it 
better that would be really useful.

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

On Thu, Mar 3, 2016 at 9:50 AM, Antonio Gomes Rodrigues <ra0...@gmail.com>
wrote:

> Hi,
>
> I will continu with this discussion and open new if necessary
>
>
>
> 2016-03-02 20:37 GMT+01:00 Philippe Mouawad <philippe.moua...@gmail.com>:
>
> > Hi
> > Thanks for contrib.
> > Maybe you should open a new discussion.
> > On Wednesday, March 2, 2016, Antonio Gomes Rodrigues <ra0...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > My opinion about the remaining Work before Release of 3.0.
> > >
> > > JMeter seems to have a significant technical debt and I think it's the
> > > moment (because we can broke the compatibility) to reduce it
> > >
> > > The technical debt I see:
> > > Use of no maintained framework (Log, ORO)
> >
> >
> > Big work has been done already in the upcoming 3.0 ( 7 legacy jars and
> > dependencies dropped)
> > Big spring cleanup and java7 sugar syntax thanks to many PRs and work by
> > team.
> >
> > I know there was a lot of work and I appreciate it
>
> About Apache ORO which is not maintain anymore, if we need to drop it we
> need to check if it break compatibility.
>
It does

> And if the response is yes it will be great to drop it before 3.0 release
>

We can also break it in 3.1.This subject needs to be carefully thought
about as this can be very annoying to users.
I prefer a rapid release of 3.0, I think many users are waiting for it and
we are now approaching 1 year without release.


>
>
> >
> >
> > > Old school GUI
> >
> >
> > That's big work
> >
> > Very big work and I don't know if it's needed.
> But each time a newbie see JMeter for the first time, the reaction is "WTF
> with the GUI"
>

It is true, but would have to wait a 3.1 IMO


> For example LoadRuner which have a Ols school GUI for a long time have work
> in it some years ago to modernize it
>
>
> >
> > > Complex GUI
> >
> >
> > Some work has been done in 3.0 but there is still ways to improve and
> > simplify.
> >
> > Feel free to open detailed proposals or Bugzillas
> >
> I will try to make some PR and if it's too complicated for me I will open
> Bugzillas
>



>
>
> >
> >
> > > Lack of official feature (JMeter plugin, Maven plugin, etc.)
> >
> >
> > non official maven plugin exists and works rather nicely.
> > What do you mean by JMeter plugin ?
> >
>
> In general I have very bad experience with:
> third party plugin (not well integrate, not well tested, not up to date
> with the latest release, etc.)
> Plugin maintained by only one person (less motivation by the developer,
> etc.)
>
> I have write my post to quicly, JMeter plugin = Jenkins plugin
>
> If you check the homepage of the plugin:
> https://wiki.jenkins-ci.org/display/JENKINS/Performance+Plugin
>
> The plugin is tagged "This plugin is up for adoption. No active maintainer
> - Looking for new maintainer"
>
> It's not reassuring if you are a newbie and/or want to have a supported
> plugin
>
>
> >
> >
> > > Unused (to my opinion) element (Monitor Results listener, etc.)
> >
> > +1
> >
> > > In Listener element, mix between Debug listener (Assertion Results,
> etc.)
> >
> > and "real" listener (Summary Report, etc.)
> >
> > +1
> >
> > > Default value of parameter (I still don't understand why "Generate
> parent
> > > sample" is not true by default in Transaction Controller)
> >
> > 2 reason for keeping it:
> > - report/dashboard requires it to compute hits/s and detailed error
> report.
> > JMeter-plugins graphs also
> > - there are bugs in Parent sampler mode for now, 2 were fixed for 3.0
> but 2
> > remain.
> >
> >
> >
> > > etc.
> >
> >
> > Could you give more details ?
> >
> >
> > >
> > > Some of them are complex to fix but other can be fix if anybody are ok
> to
> > > brake the compatibility
> > >
> > >
> > > Regards
> > > Antonio
> > >
> > > Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
> > > www.avast.com
> > > <
> > >
> >
> https://www.avast.com/fr-fr/lp-safe-emailing?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=OA-2109-A
> > > >
> > > <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > >
> > > 2016-02-28 19:15 GMT+01:00 Philippe Mouawad &

Re: Remaining Work before Release of 3.0

[Antonio Gomes Rodrigues]

Hi,

I will continu with this discussion and open new if necessary



2016-03-02 20:37 GMT+01:00 Philippe Mouawad <philippe.moua...@gmail.com>:

> Hi
> Thanks for contrib.
> Maybe you should open a new discussion.
> On Wednesday, March 2, 2016, Antonio Gomes Rodrigues <ra0...@gmail.com>
> wrote:
>
> > Hi,
> >
> > My opinion about the remaining Work before Release of 3.0.
> >
> > JMeter seems to have a significant technical debt and I think it's the
> > moment (because we can broke the compatibility) to reduce it
> >
> > The technical debt I see:
> > Use of no maintained framework (Log, ORO)
>
>
> Big work has been done already in the upcoming 3.0 ( 7 legacy jars and
> dependencies dropped)
> Big spring cleanup and java7 sugar syntax thanks to many PRs and work by
> team.
>
> I know there was a lot of work and I appreciate it

About Apache ORO which is not maintain anymore, if we need to drop it we
need to check if it break compatibility.
And if the response is yes it will be great to drop it before 3.0 release


>
>
> > Old school GUI
>
>
> That's big work
>
> Very big work and I don't know if it's needed.
But each time a newbie see JMeter for the first time, the reaction is "WTF
with the GUI"
For example LoadRuner which have a Ols school GUI for a long time have work
in it some years ago to modernize it


>
> > Complex GUI
>
>
> Some work has been done in 3.0 but there is still ways to improve and
> simplify.
>
> Feel free to open detailed proposals or Bugzillas
>
I will try to make some PR and if it's too complicated for me I will open
Bugzillas


>
>
> > Lack of official feature (JMeter plugin, Maven plugin, etc.)
>
>
> non official maven plugin exists and works rather nicely.
> What do you mean by JMeter plugin ?
>

In general I have very bad experience with:
third party plugin (not well integrate, not well tested, not up to date
with the latest release, etc.)
Plugin maintained by only one person (less motivation by the developer,
etc.)

I have write my post to quicly, JMeter plugin = Jenkins plugin

If you check the homepage of the plugin:
https://wiki.jenkins-ci.org/display/JENKINS/Performance+Plugin

The plugin is tagged "This plugin is up for adoption. No active maintainer
- Looking for new maintainer"

It's not reassuring if you are a newbie and/or want to have a supported
plugin


>
>
> > Unused (to my opinion) element (Monitor Results listener, etc.)
>
> +1
>
> > In Listener element, mix between Debug listener (Assertion Results, etc.)
>
> and "real" listener (Summary Report, etc.)
>
> +1
>
> > Default value of parameter (I still don't understand why "Generate parent
> > sample" is not true by default in Transaction Controller)
>
> 2 reason for keeping it:
> - report/dashboard requires it to compute hits/s and detailed error report.
> JMeter-plugins graphs also
> - there are bugs in Parent sampler mode for now, 2 were fixed for 3.0 but 2
> remain.
>
>
>
> > etc.
>
>
> Could you give more details ?
>
>
> >
> > Some of them are complex to fix but other can be fix if anybody are ok to
> > brake the compatibility
> >
> >
> > Regards
> > Antonio
> >
> > Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
> > www.avast.com
> > <
> >
> https://www.avast.com/fr-fr/lp-safe-emailing?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=OA-2109-A
> > >
> > <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >
> > 2016-02-28 19:15 GMT+01:00 Philippe Mouawad <philippe.moua...@gmail.com
> > <javascript:;>>:
> >
> > > Hello,
> > > I implemented Bug 58936 which distributes now nightly builds as regular
> > > released versions, so they can be used much more easily.
> > >
> > > Regards
> > >
> > > On Sat, Feb 27, 2016 at 11:06 AM, Philippe Mouawad <
> > > philippe.moua...@gmail.com <javascript:;>> wrote:
> > >
> > > > Hello
> > > > I had a look at bugs, enhancements and pending mailing lists
> > discussions.
> > > >
> > > > After release of HttpClient 4.5.2, we are now ready to finalize the
> 3.0
> > > > version.
> > > >
> > > > I added a Tag "fix_before_3.0" on issues that are pending :
> > > >
> > > > Here is the list:
> > > > 59083 JMeter HTTP NEW --- HTTP Request : Make
> > Method
> > > > field editable so that additional methods (Webdav) can be added
> easily

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

Hi
Thanks for contrib.
Maybe you should open a new discussion.
On Wednesday, March 2, 2016, Antonio Gomes Rodrigues <ra0...@gmail.com>
wrote:

> Hi,
>
> My opinion about the remaining Work before Release of 3.0.
>
> JMeter seems to have a significant technical debt and I think it's the
> moment (because we can broke the compatibility) to reduce it
>
> The technical debt I see:
> Use of no maintained framework (Log, ORO)


Big work has been done already in the upcoming 3.0 ( 7 legacy jars and
dependencies dropped)
Big spring cleanup and java7 sugar syntax thanks to many PRs and work by
team.



> Old school GUI


That's big work


> Complex GUI


Some work has been done in 3.0 but there is still ways to improve and
simplify.

Feel free to open detailed proposals or Bugzillas


> Lack of official feature (JMeter plugin, Maven plugin, etc.)


non official maven plugin exists and works rather nicely.
What do you mean by JMeter plugin ?


> Unused (to my opinion) element (Monitor Results listener, etc.)

+1

> In Listener element, mix between Debug listener (Assertion Results, etc.)

and "real" listener (Summary Report, etc.)

+1

> Default value of parameter (I still don't understand why "Generate parent
> sample" is not true by default in Transaction Controller)

2 reason for keeping it:
- report/dashboard requires it to compute hits/s and detailed error report.
JMeter-plugins graphs also
- there are bugs in Parent sampler mode for now, 2 were fixed for 3.0 but 2
remain.



> etc.


Could you give more details ?


>
> Some of them are complex to fix but other can be fix if anybody are ok to
> brake the compatibility
>
>
> Regards
> Antonio
>
> Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
> www.avast.com
> <
> https://www.avast.com/fr-fr/lp-safe-emailing?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=OA-2109-A
> >
> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> 2016-02-28 19:15 GMT+01:00 Philippe Mouawad <philippe.moua...@gmail.com
> <javascript:;>>:
>
> > Hello,
> > I implemented Bug 58936 which distributes now nightly builds as regular
> > released versions, so they can be used much more easily.
> >
> > Regards
> >
> > On Sat, Feb 27, 2016 at 11:06 AM, Philippe Mouawad <
> > philippe.moua...@gmail.com <javascript:;>> wrote:
> >
> > > Hello
> > > I had a look at bugs, enhancements and pending mailing lists
> discussions.
> > >
> > > After release of HttpClient 4.5.2, we are now ready to finalize the 3.0
> > > version.
> > >
> > > I added a Tag "fix_before_3.0" on issues that are pending :
> > >
> > > Here is the list:
> > > 59083 JMeter HTTP NEW --- HTTP Request : Make
> Method
> > > field editable so that additional methods (Webdav) can be added easily
> > =>
> > > PATCH nearly ready to be commited
> > > 59038 JMeter HTTP NEW --- Deprecate HTTPClient 3.1
> > > related elements => Some deprecation work to do
> > > 59033 JMeter HTTP NEW --- Parallel Download : Add
> CSS
> > > Parsing to extract links from CSS files => Patch Part1 ready to
> > commit,
> > > we could stop for now and complete it in 3.1 by adding an
> implementation
> > > similar to HTMLRegexParser that extracts url()
> > > 58986 JMeter Main REOP --- Report/Dashboard reuses
> > the
> > > same output directory
> > > => Waiting for sebb answer, not a lot of work
> > > 58807 JMeter HTTP NEED ---
> > > https.use.cached.ssl.context=false is broken
> > > => Patch waiting to be commited
> > > 57182 JMeter Main NEW --- Better defaults : Save
> idle
> > > time by default
> > > => Not mandatory
> > >
> > >
> > > I will work on:
> > >
> > >- 59038
> > >- 58986 if you are ok with my solution last comment on bug
> > >
> > >
> > > Besides this we had some documentation update:
> > >
> > >- Screenshots
> > >- New and Noteworthy section which should be very rich
> > >
> > >
> > > Once this is done, for release, what do you think of the following:
> > >
> > >- We send on user mailing list and twitter a message to ask users to
> > >test nightly build and wait for 1 week for feedback
> > >- We then start the release process
> > >
> > >
> > >
> > > Regards
> > > Philippe
> > >
> >
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
> >
>


-- 
Cordialement.
Philippe Mouawad.

Re: Remaining Work before Release of 3.0

[Antonio Gomes Rodrigues]

Hi,

My opinion about the remaining Work before Release of 3.0.

JMeter seems to have a significant technical debt and I think it's the
moment (because we can broke the compatibility) to reduce it

The technical debt I see:
Use of no maintained framework (Log, ORO)
Old school GUI
Complex GUI
Lack of official feature (JMeter plugin, Maven plugin, etc.)
Unused (to my opinion) element (Monitor Results listener, etc.)
In Listener element, mix between Debug listener (Assertion Results, etc.)
and "real" listener (Summary Report, etc.)
Default value of parameter (I still don't understand why "Generate parent
sample" is not true by default in Transaction Controller)
etc.

Some of them are complex to fix but other can be fix if anybody are ok to
brake the compatibility


Regards
Antonio

Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
www.avast.com
<https://www.avast.com/fr-fr/lp-safe-emailing?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=OA-2109-A>
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2016-02-28 19:15 GMT+01:00 Philippe Mouawad <philippe.moua...@gmail.com>:

> Hello,
> I implemented Bug 58936 which distributes now nightly builds as regular
> released versions, so they can be used much more easily.
>
> Regards
>
> On Sat, Feb 27, 2016 at 11:06 AM, Philippe Mouawad <
> philippe.moua...@gmail.com> wrote:
>
> > Hello
> > I had a look at bugs, enhancements and pending mailing lists discussions.
> >
> > After release of HttpClient 4.5.2, we are now ready to finalize the 3.0
> > version.
> >
> > I added a Tag "fix_before_3.0" on issues that are pending :
> >
> > Here is the list:
> > 59083 JMeter HTTP NEW --- HTTP Request : Make Method
> > field editable so that additional methods (Webdav) can be added easily
> =>
> > PATCH nearly ready to be commited
> > 59038 JMeter HTTP NEW --- Deprecate HTTPClient 3.1
> > related elements => Some deprecation work to do
> > 59033 JMeter HTTP NEW --- Parallel Download : Add CSS
> > Parsing to extract links from CSS files => Patch Part1 ready to
> commit,
> > we could stop for now and complete it in 3.1 by adding an implementation
> > similar to HTMLRegexParser that extracts url()
> > 58986 JMeter Main REOP --- Report/Dashboard reuses
> the
> > same output directory
> > => Waiting for sebb answer, not a lot of work
> > 58807 JMeter HTTP NEED ---
> > https.use.cached.ssl.context=false is broken
> > => Patch waiting to be commited
> > 57182 JMeter Main NEW --- Better defaults : Save idle
> > time by default
> > => Not mandatory
> >
> >
> > I will work on:
> >
> >- 59038
> >- 58986 if you are ok with my solution last comment on bug
> >
> >
> > Besides this we had some documentation update:
> >
> >- Screenshots
> >- New and Noteworthy section which should be very rich
> >
> >
> > Once this is done, for release, what do you think of the following:
> >
> >- We send on user mailing list and twitter a message to ask users to
> >test nightly build and wait for 1 week for feedback
> >- We then start the release process
> >
> >
> >
> > Regards
> > Philippe
> >
>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>

Re: Remaining Work before Release of 3.0

[Philippe Mouawad]

Hello,
I implemented Bug 58936 which distributes now nightly builds as regular
released versions, so they can be used much more easily.

Regards

On Sat, Feb 27, 2016 at 11:06 AM, Philippe Mouawad <
philippe.moua...@gmail.com> wrote:

> Hello
> I had a look at bugs, enhancements and pending mailing lists discussions.
>
> After release of HttpClient 4.5.2, we are now ready to finalize the 3.0
> version.
>
> I added a Tag "fix_before_3.0" on issues that are pending :
>
> Here is the list:
> 59083 JMeter HTTP NEW --- HTTP Request : Make Method
> field editable so that additional methods (Webdav) can be added easily  =>
> PATCH nearly ready to be commited
> 59038 JMeter HTTP NEW --- Deprecate HTTPClient 3.1
> related elements => Some deprecation work to do
> 59033 JMeter HTTP NEW --- Parallel Download : Add CSS
> Parsing to extract links from CSS files => Patch Part1 ready to commit,
> we could stop for now and complete it in 3.1 by adding an implementation
> similar to HTMLRegexParser that extracts url()
> 58986 JMeter Main REOP --- Report/Dashboard reuses the
> same output directory
> => Waiting for sebb answer, not a lot of work
> 58807 JMeter HTTP NEED ---
> https.use.cached.ssl.context=false is broken
> => Patch waiting to be commited
> 57182 JMeter Main NEW --- Better defaults : Save idle
> time by default
> => Not mandatory
>
>
> I will work on:
>
>- 59038
>- 58986 if you are ok with my solution last comment on bug
>
>
> Besides this we had some documentation update:
>
>- Screenshots
>- New and Noteworthy section which should be very rich
>
>
> Once this is done, for release, what do you think of the following:
>
>- We send on user mailing list and twitter a message to ask users to
>test nightly build and wait for 1 week for feedback
>- We then start the release process
>
>
>
> Regards
> Philippe
>



-- 
Cordialement.
Philippe Mouawad.