Javen O'Neal-2 wrote > How many releases into the 4.x series will we allow for API breaks? If we > need to make all of our API changes by the time 4.0 final releases, then > we > might have a few more 4.0 betas than other releases (and probably wouldn't > be ready for 4.0 final until Q2 2018).
I forgot to mention a voting about semantic versioning: d) apply semantic versioning for 4.0.0+? So we would have 4.0.1/.2... instead of the betas. The problem with our beta-approach vs. semantic versioning is, that we can have breaks in newly introduced APIs - and patch/minor versions ought to be backwards-compatible. If this contradiction is ok for you, I would say, as long as we keep pushing the patch versions, we can keep changing the API. Yegor Kozlov-4 wrote > JDK 1.8 might be an acceptance killer for Apache Tika, one of our major > consumers, as Tika still compiles on JDK 1.7. It makes sense to drop a > line > to @tika-dev and confirm it. When writing the initial mail, I thought about this. ... but I like to have the feedback first of the POI PMCs. Andi -- View this message in context: http://apache-poi.1045710.n5.nabble.com/Discussions-on-POI-4-0-Java7-8-voting-tp5728560p5728564.html Sent from the POI - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
