1 |
dashley |
23 |
<html> |
2 |
|
|
|
3 |
|
|
<head> |
4 |
|
|
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> |
5 |
|
|
<meta name="GENERATOR" content="Microsoft FrontPage 4.0"> |
6 |
|
|
<meta name="ProgId" content="FrontPage.Editor.Document"> |
7 |
|
|
<title>ESRG Release Version Number Assignment Policy</title> |
8 |
|
|
<base target="main"> |
9 |
|
|
</head> |
10 |
|
|
|
11 |
|
|
<body background="../../bkgnds/bk10.gif"> |
12 |
|
|
|
13 |
|
|
<p align="center"><b><font size="4">ESRG Release Version Number Assignment Policy</font></b></p> |
14 |
|
|
<hr> |
15 |
|
|
<p>To maintain good administrative order, there is a policy for how version |
16 |
|
|
numbers of materials released by the ESRG are assigned, and how the materials |
17 |
|
|
are released. Here are the policies.</p> |
18 |
|
|
|
19 |
|
|
<ol> |
20 |
|
|
<li><b>All materials and downloads are released simultaneously with the same |
21 |
|
|
version number.</b> (This means that every release is a |
22 |
|
|
"full" release. It is possible or even likely that some |
23 |
|
|
materials are unchanged from release to release except for the version |
24 |
|
|
number.)<br> |
25 |
|
|
</li> |
26 |
|
|
<li><b>There are NO patches.</b> If a bug is not critical, it can be |
27 |
|
|
ignored until the next release. If a bug is critical, it can |
28 |
|
|
accelerate the next release (perhaps the release would be made with just the |
29 |
|
|
bug fix). Releases are "all or nothing", and there is no |
30 |
|
|
notion of a "patch".<br> |
31 |
|
|
</li> |
32 |
|
|
<li><b>There are NO "silent" releases.</b> To avoid confusion, |
33 |
|
|
any change in the set of released materials requires another version number. Allowing a |
34 |
|
|
situation where two things which are [even subtly] different but have the |
35 |
|
|
same version number causes confusion.<br> |
36 |
|
|
</li> |
37 |
|
|
<li><b>Version numbers are of the form:</b><br> |
38 |
|
|
<br> |
39 |
|
|
<b><Major number>.<2-Digit Minor number><Optional |
40 |
|
|
"A" for "alpha" release>.<2-digit bug fix |
41 |
|
|
number></b><br> |
42 |
|
|
<br> |
43 |
|
|
For example, these are valid version numbers and their meanings:<br> |
44 |
|
|
<ul> |
45 |
|
|
<li><b>1.06A.00</b>: This is the "alpha" (trial, or not |
46 |
|
|
fully stable) release of version 1.06. (Note that "A" is |
47 |
|
|
normally only used with a bug fix number of "00".) </li> |
48 |
|
|
<li><b>1.07.09</b>: This is the ninth bug fix release of stable |
49 |
|
|
release version 1.07.00.<br> |
50 |
|
|
</li> |
51 |
|
|
</ul> |
52 |
|
|
<li><b>Version numbers normally follow this sequential cycle:</b> |
53 |
|
|
<ul> |
54 |
|
|
<li>An alpha release, such as "v1.06A.00".</li> |
55 |
|
|
<li>A stable release, which will consist of the alpha release with any bugs |
56 |
|
|
corrected, such as "v1.06.00".</li> |
57 |
|
|
<li>Bug fixes to the stable release, such as "v1.06.01", |
58 |
|
|
"v1.06.02", etc.</li> |
59 |
|
|
</ul> |
60 |
|
|
</li> |
61 |
|
|
</ol> |
62 |
|
|
<hr> |
63 |
|
|
<p align="center" style="margin-top: -2; margin-bottom: -1"><font size="1">This |
64 |
|
|
web page is maintained by <a href="mailto:dtashley@users.sourceforge.net">David |
65 |
|
|
T. Ashley</a>.<br>$Header: /cvsroot/esrg/sfesrg/esrgweba/htdocs/devels/version_nums/vn_policy.htm,v 1.2 2003/04/27 08:11:08 dtashley Exp $</font></p> |
66 |
|
|
<hr noshade size="5"> |
67 |
|
|
|
68 |
|
|
</body> |
69 |
|
|
|
70 |
|
|
</html> |