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&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_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. >
