JMeter 3.0 is the first release which drop the Java 6 support. The
history of JMeter releases show that the drop of old java version is
long (several year after the end of life)
Drop the Java 7 support for the 3.1 or 3.2 seems not follow the same
strategy that the past.
Perhaps, we need to think about 2 branches:
* branch 3.0.x, a sort of LTS release with Java 7 support (back-porting
some bug patches from the 4.x branch to this branch)
* branch 4.x with the last supported Java version, latest frameworks and
innovation.
Have 2 living branches need more work for the committers. But I think
it's a good compromise between the reliability of JMeter and bring
innovation inside JMeter.
On 04/08/2016 06:56, Antonio Gomes Rodrigues wrote:
+1 for Java 8
Antonio
2016-08-03 21:46 GMT+02:00 Vladimir Sitnikov <sitnikov.vladi...@gmail.com>:
Philippe Mouawad <philippe.moua...@gmail.com>:
Felix wanted a bugfix release ASAP, I support this idea.
It could be named 3.1 as there are some enhancements, for me it could
come
soon.
But my proposal on Java 8 is for N+2 (3.2 (not 3.1 as I wrote) or 4)
release
No problem with that.
Even N+3 would be fine provided we invent some way of releasing more often
than once a year.
Vladimir
