Hi *, my plan was to wait for commons-compress 1.17 and then release poi 4.0.0.
I'm currently trying to use jigsaw modules and would like rather push module refactoring for jigsaw than backporting stuff, but if you list the bugzilla issue for a 3.X maintenance release I'm happy to merge those. I'm not really into android development, but I guess providing android / Java 9+ compatibility [1] are diametrically opposed goals, right? So we might need to backport stuff anyways for a while ... Andi [1] https://stackoverflow.com/questions/47627499/does-android-studio-3-support-java-9-for-android-development https://developer.android.com/studio/write/java8-support On 5/4/18 11:23 AM, Nick Burch wrote: > Hi All > > We released 3.17 back in September, which is over 6 months ago. The changelog > <http://poi.apache.org/changes.html> says we've done quite a bit > since then > > What do we think about another release? Do a 3.18, then breaking changes for > 4.0 afterwards to release that in the summer? Or just finish stuff up and > push 4.0 out soon? > > Nick >
signature.asc
Description: OpenPGP digital signature
