https://bz.apache.org/bugzilla/show_bug.cgi?id=60713
Andreas Beeker changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bz.apache.org/bugzilla/show_bug.cgi?id=60713
Andreas Beeker changed:
What|Removed |Added
Version|unspecified |4.0-dev
Hardware|PC
A. +1
B. -0 for 1.6
C. +1
Technical there's no need for upgrading to 1.8 and I haven't investigated which
projects depend on XmlBeans and have already upgraded to 1.8. If we choose Java
1.6 for XmlBeans 3.0.0, we will hardly soon switch to Java 1.8.
I'm happy that POI has switched to 1.8, but
A. +1
B. 1.6
C. -0
Gesendet mit BlueMail
Originale Nachricht
Von: "pj.fanning"
Gesendet: Thu Jun 14 05:51:22 GMT-03:00 2018
An: dev@poi.apache.org
Betreff: XMLBeans 3.0.0 votes
Can I get votes on the following?
A. Stop supporting Java 1.4
B. If we stop supporting Java
A. +1
B. 1.6
C. +1
-Original Message-
From: pj.fanning [mailto:fannin...@yahoo.com]
Sent: Thursday, June 14, 2018 4:51 AM
To: dev@poi.apache.org
Subject: XMLBeans 3.0.0 votes
Can I get votes on the following?
A. Stop supporting Java 1.4
B. If we stop supporting Java 1.4, do set Java
Can I get votes on the following?
A. Stop supporting Java 1.4
B. If we stop supporting Java 1.4, do set Java 1.6 or Java 1.8 as the
minimum?
C. Do we call the next release 3.0.0?
It's inconvenient to keep supporting Java 1.4 builds.
We don't need to use Java APIs that have been introduced after