-
Bug
-
Resolution: Fixed
-
P3
-
None
-
b25
Currently, the man pages are stored as troff (a text format) in the open repo, and a content-wise identical copy is stored as markdown (another text format) in the closed repo.
Since markdown is preferred to troff in terms of editing, we make changes to the man pages in markdown and then convert it to troff.
This closed-markdown to open-troff processing needs to be done manually by an Oracle engineer. This is done regularly at the start and end of a new release cycle, adding to the burden of creating a new release. It is also done (if any of the reviewers knows about the process) whenever an Oracle engineer updates a man page. If a community contributor changes the behavior of a tool, an Oracle engineer needs to change the documentation for them, since they cannot do it themselves.
Since markdown is preferred to troff in terms of editing, we make changes to the man pages in markdown and then convert it to troff.
This closed-markdown to open-troff processing needs to be done manually by an Oracle engineer. This is done regularly at the start and end of a new release cycle, adding to the burden of creating a new release. It is also done (if any of the reviewers knows about the process) whenever an Oracle engineer updates a man page. If a community contributor changes the behavior of a tool, an Oracle engineer needs to change the documentation for them, since they cannot do it themselves.
- causes
-
JDK-8348975 Broken links in the JDK 24 JavaDoc API documentation, build 33
-
- Resolved
-
- links to
-
Commit(master) openjdk/jdk/475feb06
-
Review(master) openjdk/jdk/22081