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="DITA Open Toolkit release management"/>
|
---|
11 | <meta name="abstract" content="The DITA-OT project works with an agile development process; it releases test (milestone) builds approximately every month, and it encourages feedback on the test builds while function is being developed. Stable releases are typically issued approximately every six months."/>
|
---|
12 | <meta name="description" content="The DITA-OT project works with an agile development process; it releases test (milestone) builds approximately every month, and it encourages feedback on the test builds while function is being developed. Stable releases are typically issued approximately every six months."/>
|
---|
13 | <meta name="DC.subject" content="DITA-OT project, release management"/>
|
---|
14 | <meta name="keywords" content="DITA-OT project, release management"/>
|
---|
15 | <meta name="DC.Relation" scheme="URI" content="../admin/DevelopmentProcess.html"/>
|
---|
16 | <meta name="DC.Relation" scheme="URI" content="https://lists.sourceforge.net/lists/listinfo/dita-ot-developer"/>
|
---|
17 | <meta name="DC.Relation" scheme="URI" content="https://github.com/dita-ot/dita-ot/wiki/Meeting-minutes"/>
|
---|
18 | <meta name="DC.Format" content="XHTML"/>
|
---|
19 | <meta name="DC.Identifier" content="ditaopentoolkitreleaselifecycle"/>
|
---|
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>DITA Open Toolkit release management</title>
|
---|
24 | </head>
|
---|
25 | <body id="ditaopentoolkitreleaselifecycle">
|
---|
26 |
|
---|
27 |
|
---|
28 | <h1 class="title topictitle1">DITA Open Toolkit release management</h1>
|
---|
29 |
|
---|
30 |
|
---|
31 |
|
---|
32 |
|
---|
33 | <div class="body"><p class="shortdesc">The DITA-OT project works with an agile development process; it releases test (milestone)
|
---|
34 | builds approximately every month, and it encourages feedback on the test builds while function is
|
---|
35 | being developed. Stable releases are typically issued approximately every six months.</p>
|
---|
36 |
|
---|
37 | <p class="p">Each iteration begins with a meeting of project contributors. The meeting minutes are stored on
|
---|
38 | the project Wiki and are available to the public. Active contributors are directly invited to these
|
---|
39 | meetings, but anybody interested in the DITA-OT development is welcome to attend. If you are
|
---|
40 | interested in attending these meetings, join the dita-ot-developer mailing list and send a note to
|
---|
41 | the list or list owners.</p>
|
---|
42 |
|
---|
43 | <div class="p">Each iteration kick-off meeting covers the following topics:<ul class="ul">
|
---|
44 | <li class="li">Issues from the previous iteration</li>
|
---|
45 |
|
---|
46 | <li class="li">Plans from each contributor for the upcoming iteration or for new work that will span multiple
|
---|
47 | iterations</li>
|
---|
48 |
|
---|
49 | <li class="li">Design discussion for any significant planned features or fixes</li>
|
---|
50 |
|
---|
51 | <li class="li">Longer-term plans for contributions to the current or following release</li>
|
---|
52 |
|
---|
53 | <li class="li">(As needed) Other project issues or hot topics, such as changes to the test and build process,
|
---|
54 | interest from new contributors, etc.</li>
|
---|
55 |
|
---|
56 | </ul>
|
---|
57 | </div>
|
---|
58 |
|
---|
59 | <div class="p">The kick-off meeting for the final iteration before a stable build covers the following topics:<ul class="ul">
|
---|
60 | <li class="li">Evaluation of what is allowed in the iteration; the final iteration typically has no major
|
---|
61 | changes in order to assure quality in the stable build.</li>
|
---|
62 |
|
---|
63 | <li class="li">Assessment of whether all release notes and other artifacts are up-to-date and ready for a final
|
---|
64 | build.</li>
|
---|
65 |
|
---|
66 | </ul>
|
---|
67 | </div>
|
---|
68 |
|
---|
69 | <p class="p">When an iteration is complete, the build is uploaded to SourceForge. Test builds are placed in
|
---|
70 | the <span class="ph filepath">Latest Test Build</span> folder. At the end of a release cycle, the builds are
|
---|
71 | loaded to the <span class="ph filepath">Stable Release</span> folder, and the project information is updated to
|
---|
72 | reflect the latest release.</p>
|
---|
73 |
|
---|
74 | </div>
|
---|
75 |
|
---|
76 | <div class="related-links">
|
---|
77 | <div class="familylinks">
|
---|
78 | <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>
|
---|
79 | </div>
|
---|
80 | <div class="relinfo"><strong>Related information</strong><br/>
|
---|
81 | <div><a class="link" href="https://lists.sourceforge.net/lists/listinfo/dita-ot-developer" target="_blank">https://lists.sourceforge.net/lists/listinfo/dita-ot-developer</a></div>
|
---|
82 | <div><a class="link" href="https://github.com/dita-ot/dita-ot/wiki/Meeting-minutes" target="_blank">https://github.com/dita-ot/dita-ot/wiki/Meeting-minutes</a></div>
|
---|
83 | </div>
|
---|
84 | </div>
|
---|
85 |
|
---|
86 | </body>
|
---|
87 | </html>
|
---|