| 1 | <?xml version="1.0" encoding="UTF-8"?>
|
|---|
| 2 | <!DOCTYPE html
|
|---|
| 3 | PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|---|
| 4 | <html xml:lang="en-us" lang="en-us">
|
|---|
| 5 | <head>
|
|---|
| 6 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
|
|---|
| 7 | <meta name="copyright" content="(C) Copyright 2005"/>
|
|---|
| 8 | <meta name="DC.rights.owner" content="(C) Copyright 2005"/>
|
|---|
| 9 | <meta name="DC.Type" content="topic"/>
|
|---|
| 10 | <meta name="DC.Title" content="Feature requests and defect reports"/>
|
|---|
| 11 | <meta name="abstract" content="Feature requests and defect reports can be submitted at any time through the project page at GitHub."/>
|
|---|
| 12 | <meta name="description" content="Feature requests and defect reports can be submitted at any time through the project page at GitHub."/>
|
|---|
| 13 | <meta name="DC.subject" content="DITA-OT project, defect reports, feature requests"/>
|
|---|
| 14 | <meta name="keywords" content="DITA-OT project, defect reports, feature requests"/>
|
|---|
| 15 | <meta name="DC.Relation" scheme="URI" content="../admin/DevelopmentProcess.html"/>
|
|---|
| 16 | <meta name="DC.Relation" scheme="URI" content="https://github.com/dita-ot/dita-ot/issues"/>
|
|---|
| 17 | <meta name="DC.Relation" scheme="URI" content="https://github.com/dita-ot/dita-ot/issues"/>
|
|---|
| 18 | <meta name="DC.Format" content="XHTML"/>
|
|---|
| 19 | <meta name="DC.Identifier" content="fixesandfeatures"/>
|
|---|
| 20 | <meta name="DC.Language" content="en-us"/>
|
|---|
| 21 | <link rel="stylesheet" type="text/css" href="../commonltr.css"/>
|
|---|
| 22 | <link rel="stylesheet" type="text/css" href="../dita-ot-doc.css"/>
|
|---|
| 23 | <title>Feature requests and defect reports</title>
|
|---|
| 24 | </head>
|
|---|
| 25 | <body id="fixesandfeatures">
|
|---|
| 26 |
|
|---|
| 27 |
|
|---|
| 28 | <h1 class="title topictitle1">Feature requests and defect reports</h1>
|
|---|
| 29 |
|
|---|
| 30 |
|
|---|
| 31 |
|
|---|
| 32 | <div class="body"><p class="shortdesc">Feature requests and defect reports can be submitted at any time through the project page
|
|---|
| 33 | at GitHub. </p>
|
|---|
| 34 |
|
|---|
| 35 | <p class="p">The core project contributors track and address bugs reported against the project; they issue
|
|---|
| 36 | patches based on urgency. The core contributors also will provide feedback on requests for new
|
|---|
| 37 | features or design changes, but they might not be able to provide development assistance.</p>
|
|---|
| 38 |
|
|---|
| 39 | <p class="p">All new bug reports or feature requests should be submitted through
|
|---|
| 40 | github: <a class="xref" href="https://github.com/dita-ot/dita-ot/issues" target="_blank">DITA-OT bug and feature tracker</a>.</p>
|
|---|
| 41 |
|
|---|
| 42 | <div class="section"><h2 class="title sectiontitle">Feature requests</h2><p class="p">The project committers periodically review new feature requests with contributors and interested
|
|---|
| 43 | parties; when possible, they make plans to implement the new features.</p>
|
|---|
| 44 | <p class="p">If an existing project contributor is interested in a new request, the item is assigned to the
|
|---|
| 45 | contributor and implemented based on the contributor's schedule. Otherwise, if the request is valid
|
|---|
| 46 | and in line with project goals, it is left open for an interested party to pick up and implement.
|
|---|
| 47 | Some requests are best implemented as a plug-in rather than in the core DITA-OT code; in those
|
|---|
| 48 | cases, project committers suggest alternatives and close the request.</p>
|
|---|
| 49 | </div>
|
|---|
| 50 |
|
|---|
| 51 | <div class="section"><h2 class="title sectiontitle">Defect reports</h2><p class="p">The project committers determine the owner of the relevant components and assign the defect to
|
|---|
| 52 | the component owner for validation and disposition. Responses, fixes, and workarounds are issued
|
|---|
| 53 | faster if the defect report includes sample files and clear instructions for reproducing the
|
|---|
| 54 | issue.</p>
|
|---|
| 55 | <p class="p">If bugs are found in the OASIS DITA DTDs or Schemas, they are fixed in the toolkit and reported
|
|---|
| 56 | to the OASIS DITA Technical Committee.</p>
|
|---|
| 57 | </div>
|
|---|
| 58 |
|
|---|
| 59 | </div>
|
|---|
| 60 |
|
|---|
| 61 | <div class="related-links">
|
|---|
| 62 | <div class="familylinks">
|
|---|
| 63 | <div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../admin/DevelopmentProcess.html" title="The DITA Open Toolkit (DITA-OT) development process is modeled after development processes for other popular and successful open-source projects, most notably Eclipse.">DITA Open Toolkit development process</a></div>
|
|---|
| 64 | </div>
|
|---|
| 65 | <div class="relinfo"><strong>Related information</strong><br/>
|
|---|
| 66 | <div><a class="link" href="https://github.com/dita-ot/dita-ot/issues" target="_blank">https://github.com/dita-ot/dita-ot/issues</a></div>
|
|---|
| 67 | <div><a class="link" href="https://github.com/dita-ot/dita-ot/issues" target="_blank">DITA-OT Bug and Feature tracker at GitHub</a></div>
|
|---|
| 68 | </div>
|
|---|
| 69 | </div>
|
|---|
| 70 |
|
|---|
| 71 | </body>
|
|---|
| 72 | </html>
|
|---|
