| 1 | <?xml version="1.0" encoding="UTF-8"?>
|
|---|
| 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN"
|
|---|
| 3 | "topic.dtd">
|
|---|
| 4 | <?Pub Sty _display FontColor="red"?>
|
|---|
| 5 | <?Pub Inc?>
|
|---|
| 6 | <topic id="fixesandfeatures" xml:lang="en-us">
|
|---|
| 7 | <title>Feature requests and defect reports</title>
|
|---|
| 8 | <shortdesc>Feature requests and defect reports can be submitted at any time through the project page
|
|---|
| 9 | at GitHub. </shortdesc>
|
|---|
| 10 | <prolog>
|
|---|
| 11 | <metadata>
|
|---|
| 12 | <keywords>
|
|---|
| 13 | <indexterm>DITA-OT project<indexterm>defect reports</indexterm><indexterm>feature
|
|---|
| 14 | requests</indexterm></indexterm>
|
|---|
| 15 | </keywords>
|
|---|
| 16 | </metadata>
|
|---|
| 17 | </prolog>
|
|---|
| 18 | <body>
|
|---|
| 19 | <p>The core project contributors track and address bugs reported against the project; they issue
|
|---|
| 20 | patches based on urgency. The core contributors also will provide feedback on requests for new
|
|---|
| 21 | features or design changes, but they might not be able to provide development assistance.</p>
|
|---|
| 22 | <p>All new bug reports or feature requests should be submitted through
|
|---|
| 23 | github: <xref keyref="dita-ot-issues"></xref>.</p>
|
|---|
| 24 | <section><title>Feature requests</title><p>The project committers periodically review new feature requests with contributors and interested
|
|---|
| 25 | parties; when possible, they make plans to implement the new features.</p><p>If an existing project contributor is interested in a new request, the item is assigned to the
|
|---|
| 26 | contributor and implemented based on the contributor's schedule. Otherwise, if the request is valid
|
|---|
| 27 | and in line with project goals, it is left open for an interested party to pick up and implement.
|
|---|
| 28 | Some requests are best implemented as a plug-in rather than in the core DITA-OT code; in those
|
|---|
| 29 | cases, project committers suggest alternatives and close the request.</p></section>
|
|---|
| 30 | <section><title>Defect reports</title><p>The project committers determine the owner of the relevant components and assign the defect to
|
|---|
| 31 | the component owner for validation and disposition. Responses, fixes, and workarounds are issued
|
|---|
| 32 | faster if the defect report includes sample files and clear instructions for reproducing the
|
|---|
| 33 | issue.</p><p>If bugs are found in the OASIS DITA DTDs or Schemas, they are fixed in the toolkit and reported
|
|---|
| 34 | to the OASIS DITA Technical Committee.</p></section>
|
|---|
| 35 | </body><?Pub Caret -2?>
|
|---|
| 36 | </topic>
|
|---|
| 37 | <?Pub *0000002220?>
|
|---|
