Second draft proposal: JEP 2.0

[Brian Beck]

An implementation of Mark's current proposal should show up in JBS 
momentarily.  Since discussion on the proposal is not yet complete, 
please consider it a prototype. There are one or two things that aren't 
quite right yet.  Most notably, the workflow for Process and 
Informational JEPs does not exist.  We will be making improvements and 
adapting to whatever changes occur as a result of the discussion over 
the next couple of weeks.

Please kick the tires and give us feedback.  You may enter "real" JEPs 
if you like but with two caveats.  First, we will make every effort to 
preserve the data as we evolve the system over the next couple of weeks, 
but there are no guarantees.  If some change is needed that can't be 
made without data loss, you may be asked to re-enter your work.  Second, 
the OpenJDK Lead may or may not be processing Submitted JEPs just yet, 
so don't expect it to proceed through the process.

Looking forward to feedback.

Brian.



On 5/5/14 2:13 PM, mark.reinhold at oracle.com wrote:
> Thanks to everyone who commented on the first draft.  I've posted a
> second draft here:
>
>      http://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html
>
> 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 [1] 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., [2]) 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.
>
> - Mark
>
>
> [1] http://mail.openjdk.java.net/pipermail/discuss/2014-April/003354.html
> [2] https://addons.mozilla.org/en-US/firefox/addon/its-all-text/