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




Reply via email to