Innovation again (was Re: Text classes)

[Mario Torre]

2017-12-06 9:40 GMT+01:00 John-Val Rose <johnvalrose at gmail.com>:
> Yes, I obviously need to know if anything I work on or design is going to
> be accepted or is even wanted by the community as a whole, and as early on
> in the process as possible.  Heck, if I had my way, JavaFX would be used to
> build everything from forms to FPS games and highly complex and performant
> 3D visualizations.  And don't say it can't be done in Java - it can.
> JavaMonkeyEngine can be used to create awesome games (for example).

If I understood correctly the change is big enough to need a JEP.
Generally, you need a JEP for new features, new API and big changes.
You don't need for bug fixes and internal refactoring. So, for
instance, adding a new port to the graphics need a JEP.

It's up to the project maintainer to say whether that should be a JEP
or not, though.

> Plus, I have never "done" a JEP but I believe it's quite a long and
> involved process (?)

Well, that doesn't mean you can avoid it ;)

I did work only with the two previous drafts of the JEP, but the
latest draft is a lot quicker (simply file a bug report basically).

The JEP is detailed here:

http://openjdk.java.net/jeps/1
http://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html

The second link is the current version, the first link is for
reference since this is where the process should be detailed, but
hasn't been merged yet.

Cheers,
Mario
-- 
pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF
Fingerprint: BA39 9666 94EC 8B73 27FA  FC7C 4086 63E3 80F2 40CF

Java Champion - Blog: http://neugens.wordpress.com - Twitter: @neugens
Proud GNU Classpath developer: http://www.classpath.org/
OpenJDK: http://openjdk.java.net/projects/caciocavallo/

Please, support open standards:
http://endsoftpatents.org/