[
https://issues.apache.org/jira/browse/HADOOP-11495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325519#comment-14325519
]
Allen Wittenauer commented on HADOOP-11495:
-------------------------------------------
bq. I'd like to restate that we should not creating huge divergences between
branch-2 and trunk unless there is a very good reason.
All of the divergences you are pointing out happened in previous JIRAs as part
of the followups to the shell code rewrite and/or other JIRAs that didn't make
their way to branch-2. In other words, yes, there was a good reason.
Incompatible and/or removal of deprecated procedures/APIs/etc should always
come with documentation changes.
If you aren't careful, you will introduce actual, real trunk dependencies in
the branch-2 code base with your patch. You're going to have to do a much more
thorough audit to catch them all. It's almost certainly better to start with
the actual branch-2 sources and convert them directly rather than play "find
all the relevant changes" as there are a lot (and, FWIW, more will be
incoming).
To that end, I'd much prefer if you decided to do this work in another JIRA
given that this one was always specifically targeted to trunk and was never
intended for branch-2. Never mind the fact that frankly I don't want my name
associated with your patch.
Thanks.
> Convert site documentation from apt to markdown
> -----------------------------------------------
>
> Key: HADOOP-11495
> URL: https://issues.apache.org/jira/browse/HADOOP-11495
> Project: Hadoop Common
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 3.0.0
> Reporter: Allen Wittenauer
> Assignee: Masatake Iwasaki
> Fix For: 3.0.0
>
> Attachments: HADOOP-11495-02.patch, HADOOP-11495-03.patch,
> HADOOP-11495-04.patch, HADOOP-11495-05.patch, HADOOP-11495-b2.001.patch,
> HADOOP-11496-00.patch, HADOOP-11496-01.patch
>
>
> Almost Plain Text (aka APT) lost. Markdown won.
> As a result, there are a ton of tools and online resources for Markdown that
> would make editing and using our documentation much easier. It would be
> extremely beneficial for the community as a whole to move from apt to
> markdown.
> This JIRA proposes to do this migration for the common project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
