Draft proposal: JEP 2.0
stefan.karlsson at oracle.com
Thu Apr 17 05:43:12 UTC 2014
On 2014-04-17 04:03, Mike Duigou wrote:
> On Apr 16 2014, at 18:14 , Jonathan Gibbons <jonathan.gibbons at oracle.com> wrote:
>> On 04/16/2014 01:20 AM, Stefan Karlsson wrote:
>>> On 2014-04-16 10:16, Staffan Larsen wrote:
>>>> On 16 apr 2014, at 09:14, Bengt Rutisson <bengt.rutisson at oracle.com> wrote:
>>>>> On 4/15/14 9:34 PM, Per Bothner wrote:
>>>>>> [Sorry for the bad message linkage - I just subscribed.]
>>>>>> On Apr 12 Mark Reinhold wrote:
>>>>>>> - Some people, including yours truly, find any amount of non-trivial
>>>>>>> text editing in a web browser to be extraordinarily painful. ...
>>>>>>> - Incoming JEPs invariably require at least some light copy-editing.
>>>>>>> Some JEPs require much more than that. ...
>>>>>> As you point out "The largest constituency for JEPs is the people who
>>>>>> read them, not those who write or edit them." I think most people
>>>>>> (even those of us more comfortable with Emacs) can handle editing
>>>>>> in a web browser.
>>>>> Totally agree.
>>>> If we can’t enable markup mode in the JIRA field, then maybe the openjdk wiki is a better place than markdown files in a mercurial repository?
>>> Is there a reason why we can't/won't enable markup mode in the JIRA field?
> I am not clear on why we need markup if we are able to have fields. Most of the current markup is to distinguish sections and fields.
Maybe it's not going to be needed, but I got the impression from Mark's
mail that we still we'll be maintaining documents outside JIRA, using
 "Now perhaps we can eventually customize JIRA and the systems around it
to overcome these issues, but unless and until we do so I think we'll
all be better served by continuing to create and maintain the bodies of
JEPs as Markdown documents in Mercurial while tracking their workflow
status and related tasks in JBS."
I just don't want the lack of Markdown / markup mode to be the reason
why we should be using separate documents outside JIRA.
>> I know we didn't enable markup mode on the fields that were used to store the info that was imported from the legacy bug system, but here we're talking about new fields. And, from the Atlassian documentation, it seems we should be able to configure the mode on a per-field basis...
>>> Renderers are configured on a per field basis. To configure a renderer for a particular field, see Specifying Field Behavior <https://confluence.atlassian.com/display/JIRA/Specifying+Field+Behavior>. Note that you can configure the same field differently for different projects and issue types — see Associating Field Behavior with Issue Types <https://confluence.atlassian.com/display/JIRA/Associating+Field+Behavior+with+Issue+Types>.
>> -- Jon
More information about the discuss