jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antonio Gomes Rodrigues <ra0...@gmail.com>
Subject Re: Start the next release 3.1 into 1-2 weeks?
Date Fri, 23 Sep 2016 19:46:14 GMT
Hi,

I have commited all my PR

bz still open in the Felix list:
 * bz 60092 (BODY empty for PUT) (patch would be similar to 60066)
 * bz 55258 remove CLOSE icon (PR available)
 * bz 59441 drop generated docs from svn (sebb points out, that the release
process would have to be adapted)


About PR 72 (https://github.com/apache/jmeter/pull/72) : MQTT plugin for
Jmeter
Someone have check if Eclipse Paho MQTT client v1.0.2 is the best choice?

Antonio



2016-09-15 20:35 GMT+02:00 Felix Schumacher <
felix.schumacher@internetallee.de>:

> Am 13.09.2016 um 16:20 schrieb Milamber:
>
>> Hello,
>>
>> Are you willing to start the next release process withing 1 to 2 weeks? I
>> can act as RM.
>>
> Great news. Thanks.
>
>>
>> The next release will keep the Java 7 support (probably this release will
>> be the last with Java 7 support).
>>
>> What are the bugs which will must be fixed before the next release?
>>
>  * bz 60092 (BODY empty for PUT) (patch would be similar to 60066)
>  * bz 60121 (CSS parser warnings) (waiting for release of backport ph-css
> (should be available soon))
>
>>
>> If you want add an improvement before the next release, please indicate
>> now.
>>
> I would like to address
>  * bz 60066 (CLOB/BLOB) (patch is ready, doc is missing)
>  * bz 60125 (TAB for delimiter in reports CSV) (patch is ready, doc is
> missing)
>  * doc for usage of SLF4J with maven
>
> Things that could/should be handled?
>  * bz 55258 remove CLOSE icon (PR available)
>  * bz 59441 drop generated docs from svn (sebb points out, that the
> release process would have to be adapted)
>
>
> Felix
>
>>
>> Milamber
>>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message