/
release.xml
49 lines (45 loc) · 1.59 KB
/
release.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "../dtd/document-v10.dtd">
<document>
<header>
<title>Release Plan</title>
<subtitle>Planning Documentation</subtitle>
<authors>
<person name="Carsten Ziegeler" email="cziegeler@apache.org"/>
<person name="David Crossley" email="crossley@apache.org"/>
</authors>
</header>
<body>
<s1 title="Timeframe">
<p>This is the current time frame for the next releases:</p>
<ul>
<li>Not schedulded yet : 2.2 Milestone 1</li>
<li>On request : 2.0.5 (bug fix release)</li>
</ul>
</s1>
<s1 title="Version 2.2 Milestone 1">
<p>Although this version might be long in the future, we already have some plans...</p>
<ul>
<li>Design and implement blocks</li>
<li>Move to a new Avalon container implementation (Merlin, Fortress or whatever)</li>
</ul>
</s1>
<s1 title="General tasks for a release">
<ul>
<li>We have many open bugs in bugzilla. These must be reviewed
and then solved (or declared invalid etc).</li>
<li>Documentation updates (this area lacks most).
Documentation must be happening all the time, and not left
until last.</li>
<li>Checking what to backport. We have components in the
latest developer versions, which might find their way into
the bugfix version line (2.0.x).</li>
<li>Ensure that licensing requirements have been met.
update jars.xml, ensure proper banner in *.java header,
verify the current LICENSE* files, ensure that external
components have suitable licensing requirements.</li>
<li>Everything we forgot...</li>
</ul>
</s1>
</body>
</document>