Second draft proposal: JEP 2.0

[Mathias Axelsson]

Hi Mark,

I think this update looks really good. One thing that is a little bit unclear to me is the matching of fields in JEP 1.0 vs JBS regarding Author, but I may have interpreted this incorrectly.

In the section Information in JBS issues (in table 1 and 2) I interpret it as:

- Reporter (JBS) maps to original author in JEP 1.0
- Author (JBS) maps to Author in JEP 1.0

The description text later on says "The Author field is used to record the original author of the JEP. It’s a free-form text field, since the original author might not have a username in JBS.".

Given this and that Reporter is set to the person filling an issue in JBS, should this instead state:

- Reporter (JBS) maps to Author (JEP 1.0)
- Author (JBS) maps to original author (JEP 1.0)

Kind regards,
Mathias

On 5 maj 2014, at 23:13, 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/