You'll sell your vote for pork? :)
If by some miracle we went with this, with so many back compat issues
with this update, I don't see why we wouldn't throw Java 1.5 in as well.
That just complicates things here though. I'd save that discussion.
Shai Erera wrote:
Does this mean we still move to Java 5 in 3.0? If so, +1 from me too.
On Tue, Aug 11, 2009 at 12:06 AM, Mark Miller <[email protected]
<mailto:[email protected]>> wrote:
Michael McCandless wrote:
Or... and this is one crazy idea... maybe we should simply
release 3.0
next, not removing any deprecated APIs until 3.1 or later. Ie,
"normal" software on having so many major changes would
release an X.0
release; I agree the "deprecation release" is unusual. This
way users
would realize/expect 3.0 to have major changes.
Mike
+1
--
- Mark
http://www.lucidimagination.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
<mailto:[email protected]>
For additional commands, e-mail: [email protected]
<mailto:[email protected]>
--
- Mark
http://www.lucidimagination.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
