Fwd: Second draft proposal: JEP 2.0
martijnverburg at gmail.com
Tue May 6 13:25:09 UTC 2014
I know several of you have expressed an interest in either starting a JEP
or wanting to work on one. I encourage you to have a good look at Mark's
new proposal and give feedback as appropriate to the discuss mailing list
(not this one).
---------- Forwarded message ----------
From: <mark.reinhold at oracle.com>
Date: 5 May 2014 22:13
Subject: Second draft proposal: JEP 2.0
To: discuss at openjdk.java.net
Thanks to everyone who commented on the first draft. I've posted a
second draft here:
The major differences from the first draft are:
- JEPs will be maintained entirely in JBS;
- The "Research" JEP type has been dropped, since long-term research
work can be tracked as subtasks of a Feature JEP;
- The standard workflow has been simplified from ten states to eight,
by removing the Planning and Funded states; and
- The workflow for Informational and Process JEPs is now defined.
Most of my concerns about JIRA not being a good system for structured,
long-form text documents  have been addressed by Brian Beck and
Tony Squier. They've implemented a Markdown plugin for JIRA so that
the bodies of JEPs can continue to be written in a reasonable markup
language, and they're customizing JIRA's CSS to fix some of its more
glaring typographical issues. These changes, in combination with a
suitable browser plugin (e.g., ) to enable editing in Emacs (or
the editor of your choice), seem a good-enough solution for those of
us who write and edit JEPs, and they will display JEPs in a way that
is just about as readable as the current archive.
Brian and Tony are working to implement the new JEP issue type in JBS.
It's not quite ready to go, so stay tuned for further information.
If you have comments or suggestions on this draft, please send them
in a public reply to this message by next Monday, 12 May 2014.
More information about the adoption-discuss