commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From henrib <hen...@apache.org>
Subject Re: [VOTE] Can the next version major version of a project require Java6? (i.e. drop Java 1.5)
Date Wed, 07 Dec 2011 11:28:45 GMT
I guess your +1 does not apply to the vote. :-)
And to be honest, javax.script is implemented by org.apache.bsf 3.1 which
runs on Java 1.5...

Nevertheless, the fair point that has been made by Matt later in this thread
is that Commons is a do-ocracy; if someone badly needs a component in Java
1.5, nothing prevents him from contributing that backport from Java6 code.

Accepting this and respecting the will of many would be quite a step forward
since it means Commons would cease forcing people to contribute new
projects/major-versions on an EOLed platform - for which they have
rightfully no interest for. 
IMHO, the Java 1.5 "release rule", besides forcing the
installation/maintenance cost of the dev platform for contributors, nurtures
the perception that Commons is just an unattractive set of obsolete
components.
And besides, nothing in the Commons charter states that components must
support 2 major versions old JDKs; stability and quality should not equate
to obsolescence.

Cheers,
Henrib

--
View this message in context: http://apache-commons.680414.n4.nabble.com/VOTE-Can-the-next-version-major-version-of-a-project-require-Java6-i-e-drop-Java-1-5-tp4160635p4168607.html
Sent from the Commons - Dev mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message