Hi Feiix, My answers inline below
On Saturday, July 7, 2018, Felix Schumacher < [email protected]> wrote: > > > Am 5. Juli 2018 22:47:19 MESZ schrieb Philippe Mouawad < > [email protected]>: > >Hello, > > > >We have currently 64 bugs/enhancements implemented in trunk that would > >deserve a Major new version 5.0 : > > Some people are more inclined to install a dot x release (like 4.1) as > they believe them to be more stable. On the opposite, lot of people think 4.1 would be minor (bug fix mainly) , and lot of blogs said about 3.0 and 4.0 that Jmeter had taken 10 years to release a major version. That’s why I think it’s better for « marketing » reason to release a 5.0 But it’s not the only reason. I believe this version deserves a major number: - The httpclient new Api migration - Report : New graph and Custom graphs - XPath 2 - the flow control improvements which will hopefully ease many use cases - Search improvements. I’ve been using it and it’s a big usability improvement for correlation - recorder enhancement, this really also makes life easier So I believe this 4.1 version would not be a correct version number as due to the new features and hc4 api migration it might require a bugfix version 5.1. But if you feel I am wrong, it’s not a problem to name it 4.1. i mentionned 5.0 in a tweet and here. 4.1 is mentioned in lot of stackoverflow answers and tweets. > But as you already anounced that the next version will be called 5.0, I > guess it will be 5.0. > > > > > - https://bz.apache.org/bugzilla/buglist.cgi?bug_ > > status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED& > > component=HTTP&component=Main&list_id=170488&order= > >Importance&product=JMeter&query_format=advanced&resolution=FIXED&target_ > > milestone=JMETER_4.1 > ><https://bz.apache.org/bugzilla/buglist.cgi?bug_ > status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED& > component=HTTP&component=Main&list_id=170488&order= > Importance&product=JMeter&query_format=advanced&resolution=FIXED&target_ > milestone=JMETER_4.1> > > > >I think last commits deserve a deep review /tests related to : > > > > - Flow Control Action > > - Result Status Action > > - Iterating Controllers > > > >If nobody finds a bug, the new version 5.0 should be released. > > I think we should have a look at the rmi port usage problems with the > listeners. what is the bug number for it ? Thanks > > Regards, > Felix > > > > > > >I propose to send a mail on user mailing list with following content: > > > >----------------------------------------------------------- > ------------------------------------------------- > > > >We'd like to release a new version 5.0 with following enhancements / > >bugfixes. > >We'd like tests and feedback from users. > >If you'd like to help testing, you can download a nightly build > >tomorrow: > > > > - https://ci.apache.org/projects/jmeter/nightlies/ > > > >Test particularly: > > > > - Recording > > - Flow Control Action (old Test Action) > >- Result Status Action (break loop, switch to next iteration of current > > loop) > > - While Controller / Loop Controller / Foreach Controller > > > >We'll be waiting for 10 days. > > > >----------------------------------------------------------- > ------------------------------------------------- > -- Cordialement. Philippe Mouawad.
