diff --git a/en_US.ISO8859-1/articles/version-guide/article.sgml b/en_US.ISO8859-1/articles/version-guide/article.sgml index aa2bdc4a6e..651c44f2d1 100644 --- a/en_US.ISO8859-1/articles/version-guide/article.sgml +++ b/en_US.ISO8859-1/articles/version-guide/article.sgml @@ -65,24 +65,24 @@ The goal of a major release is to introduce a set of new - features. Where necessary, it may be necessary to break - compatibility with previous major releases in order to advance - the state of &os;, or, occasionally, to drop features that - it is no longer feasible to support. + features. Inevitably, as new features are added to &os;, or as + older features are no longer useful or are dropped, it is + sometimes necessary to break compatibility with previous major + releases. The goal of a minor release is primarily to fix bugs and - improve performance and stability. Keeping compatibility + improve performance and stability. Keeping both source-level and binary compatibility from one minor release to another is a priority. On occasion, new features may be added to a minor release when it is believed that these other goals will not be compromised. - However, keep in mind that a release version + However, keep in mind that a release version is merely a snapshot of the source tree at a particular point in - time which is given a particular name (or tag). + time which is given a particular name (or tag). (For instance, the tag that Release Engineering assigned for the 5.4 release was RELENG_5_4_0_RELEASE.) Development always continues on what is known as the HEAD @@ -138,9 +138,9 @@ programs to be installed (termed the Ports Collection). Applications may be installed either from source, if its licensing terms allow such - redistribution (these are termed ports), - or as compiled binaries if allowed (these are termed - packages). + redistribution (these are called ports), + or as compiled binaries if allowed (these are called + packages). @@ -303,13 +303,27 @@ resources but primarily due to the amount of volunteer effort that is available. - Interested readers should also see the current - Release - Engineering Schedule and - Security - Branch Schedule. Both documents also go into much - greater depth about the background and rationale behind - these decisions. + Interested readers should also see: + + + + + + The Release Engineering Schedule + + + + + + + The Security Branch Schedule + + + + + These documents go into much greater depth about the background and + rationale behind the decisions regarding the supported branches and the + lifetime of each branch. @@ -350,7 +364,7 @@ - If you have a short-term need, need the highest degree of + If you have a short-term need, would benefit from the highest degree of stability currently available, and are not able to devote many resources to upgrading, then you will probably want to install the latest STABLE minor release and remain