Second draft proposal: JEP 2.0

[Bengt Rutisson]

Hi Mark,

Thanks for the updated JEP 2.0 proposal. Looks much better to me.

One question about the initial step of a JEP. The proposal states:

"Any particular proposal must be open for discussion for at least one 
calendar week, major holidays excepted."

This seems reasonable to me. What is not clear from this description is 
when this calendar week starts. Is it when I create the JEP in the JBS 
system or is there some kind of publish step in between as with the 1.0 
version of the JEP? Basically my question is, is there an SLA for how 
long I have to wait from creating a JEP until I can start pushing 
changes for it?

Thanks,
Bengt



On 2014-05-05 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/