| 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="ditaopentoolkitreleaselifecycle" xml:lang="en-us">
|
|---|
| 7 | <title>DITA Open Toolkit release management</title>
|
|---|
| 8 | <titlealts>
|
|---|
| 9 | <navtitle>Release management</navtitle>
|
|---|
| 10 | </titlealts>
|
|---|
| 11 | <shortdesc>The DITA-OT project works with an agile development process; it releases test (milestone)
|
|---|
| 12 | builds approximately every month, and it encourages feedback on the test builds while function is
|
|---|
| 13 | being developed. Stable releases are typically issued approximately every six months.</shortdesc>
|
|---|
| 14 | <prolog>
|
|---|
| 15 | <metadata>
|
|---|
| 16 | <keywords>
|
|---|
| 17 | <indexterm>DITA-OT project<indexterm>release management</indexterm></indexterm>
|
|---|
| 18 | </keywords>
|
|---|
| 19 | </metadata>
|
|---|
| 20 | </prolog>
|
|---|
| 21 | <body>
|
|---|
| 22 | <p>Each iteration begins with a meeting of project contributors. The meeting minutes are stored on
|
|---|
| 23 | the project Wiki and are available to the public. Active contributors are directly invited to these
|
|---|
| 24 | meetings, but anybody interested in the DITA-OT development is welcome to attend. If you are
|
|---|
| 25 | interested in attending these meetings, join the dita-ot-developer mailing list and send a note to
|
|---|
| 26 | the list or list owners.</p>
|
|---|
| 27 | <p>Each iteration kick-off meeting covers the following topics:<ul>
|
|---|
| 28 | <li>Issues from the previous iteration</li>
|
|---|
| 29 | <li>Plans from each contributor for the upcoming iteration or for new work that will span multiple
|
|---|
| 30 | iterations</li>
|
|---|
| 31 | <li>Design discussion for any significant planned features or fixes</li>
|
|---|
| 32 | <li>Longer-term plans for contributions to the current or following release</li>
|
|---|
| 33 | <li>(As needed) Other project issues or hot topics, such as changes to the test and build process,
|
|---|
| 34 | interest from new contributors, etc.</li>
|
|---|
| 35 | </ul></p>
|
|---|
| 36 | <p>The kick-off meeting for the final iteration before a stable build covers the following topics:<ul>
|
|---|
| 37 | <li>Evaluation of what is allowed in the iteration; the final iteration typically has no major
|
|---|
| 38 | changes in order to assure quality in the stable build.</li>
|
|---|
| 39 | <li>Assessment of whether all release notes and other artifacts are up-to-date and ready for a final
|
|---|
| 40 | build.</li>
|
|---|
| 41 | </ul></p>
|
|---|
| 42 | <p>When an iteration is complete, the build is uploaded to SourceForge. Test builds are placed in
|
|---|
| 43 | the <filepath>Latest Test Build</filepath> folder. At the end of a release cycle, the builds are
|
|---|
| 44 | loaded to the <filepath>Stable Release</filepath> folder, and the project information is updated to
|
|---|
| 45 | reflect the latest release.</p>
|
|---|
| 46 | </body>
|
|---|
| 47 | </topic><?Pub Caret -1?>
|
|---|
| 48 | <?Pub *0000002406?>
|
|---|
