Crib a list of features from the SCons home page.
[scons.git] / www / roadmap.html
1 <html>
2 <head>
3 </head>
4 <body>
5
6 <h2>Current Releases</h2>
7
8 <p>
9 The current "stable" release is 0.96.1.
10 </p>
11
12 <p>
13 The current testing pre-release is 0.96.92.
14 </p>
15
16 <h2>Upcoming Releases</h2>
17
18 Take these with a huge grain of salt,
19 this is very rough planning
20
21 <table>
22 <tr>
23 <th>Release</th>
24 <th>Est. Date <font size="-1">(yeah, right)</font><th>
25 <th>
26 Goals
27 </th>
28 </tr>
29 <tr>
30 <td>0.96.93</td>
31 <td>???</td>
32 <td>
33 Significant speed up of some specific configurations,
34 plus accumulated patches.
35 Fix for the one cosmetic bug found so far in 0.96.92.
36 </td>
37 </tr>
38 <tr>
39 <td>0.96.94</td>
40 <td>???</td>
41 <td>
42 Testing pre-release of the "Big Signature Refactoring,"
43 a significant re-design of internal data structures
44 to accomplish the following:
45   <ul>
46   <li>
47   Interoperability between MD5 signatures and timestamps.
48   </li>
49   <li>
50   Ability to partition the dependency graph into separate SConstruct
51   (not SConscript) files.
52   </li>
53   <li>
54   Improved performance (we hope)
55   </li>
56   </ul>
57 </td>
58 </tr>
59 <tr>
60 <td>0.97</td>
61 <td>???</td>
62 <td>
63 Wider release of the "Big Signature Refactoring."
64 More extensive field testing before
65 declaring the new internals ready to be
66 blessed as the official 1.0 release.
67 </td>
68 </tr>
69 <tr>
70 <td>1.0</td>
71 <td>???</td>
72 <td>
73 Official, stable release.
74 No 1.x release will (knowingly) break compatibility
75 or cause a rebuild on upgrade.
76 </td>
77 </tr>
78 <tr>
79 <td>2.0</td>
80 <td>???</td>
81 <td>
82 First release that will break backwards compatibility with Python 1.5.2.
83 </td>
84 </tr>
85 </table>
86
87 <!--
88
89 <h2>Upcoming Features</h2>
90
91 -->
92
93 <h2>Release Planning</h2>
94
95 <h3>Why has 1.0 still not been released?</h3>
96
97 <p>
98 As seems so common these days,
99 SCons has had an extremely lengthy "beta" period.
100 The primary goal has been to arrive at something by 1.0
101 that we feel is absolutely rock-solid-stable
102 and which people can download and use without fear of
103 broken builds or unnecessary rebuilds.
104 To get some idea of how we do this, see our
105 <a href="testing.html">testing philosophy</a> page.
106 </p>
107
108 <h3>Release numbering</h3>
109
110 <p>
111 </p>
112
113 </body>
114 </html>