OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Michael Schloh
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-re Date: 18-Oct-2004 17:41:13
Branch: HEAD Handle: 2004101816411300
Modified files:
openpkg-re releasenotes.txt
Log:
complete editing phase before adding new OpenPKG 2.2 specific text
Summary:
Revision Changes Path
1.6 +16 -14 openpkg-re/releasenotes.txt
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-re/releasenotes.txt
============================================================================
$ cvs diff -u -r1.5 -r1.6 releasenotes.txt
--- openpkg-re/releasenotes.txt 15 Oct 2004 15:08:49 -0000 1.5
+++ openpkg-re/releasenotes.txt 18 Oct 2004 15:41:13 -0000 1.6
@@ -2,14 +2,14 @@
OpenPKG Release Notes
=====================
- o $Revision: 1.5 $. The most recent update of this file can be
+ o $Revision: 1.6 $. The most recent update of this file can be
downloaded from http://cvs.openpkg.org/openpkg-re/releasenotes.txt
The history of this document, specific versions and
differences between versions can be retrieved from
http://cvs.openpkg.org/rlog?f=openpkg-re/releasenotes.txt
- o This file describes new features and major improvements introduced
- in the respective OpenPKG release. It can be of help when upgrading,
+ o This file describes new features and improvements introduced in
+ the respective OpenPKG release. It can be useful when upgrading,
especially in avoiding the most common upgrade problems.
o This file accompanies news.txt which serves as a one page
@@ -25,16 +25,15 @@
2.0 is the immediate successor of 1.3.
o It is wisest to limit as much infrastructure within a single OpenPKG
- instance to the corresponding OpenPKG version. That means that while
- it is technically possible, mixing packages from across several versions
- is not advisable.
+ instance to the corresponding OpenPKG version. Mixing packages from
+ several OpenPKG versions is unadvised.
o Be aware that as new features and improvements are added, both major
and minor OpenPKG upgrades might introduce incompatabilities with older
OpenPKG components. Packages are always upgraded to their most stable
- and up to date vendor versions. However, packages may be split,
- consolidated, or renamed as well. In rare cases packages are removed,
- leaving no upgrade path at all. OpenPKG is only released after a quality
+ and up to date vendor versions. Nevertheless, packages may be split,
+ consolidated, or renamed. In rare cases packages are removed, leaving
+ no upgrade path at all. OpenPKG is only released after a quality
assurance process confirms its integrity, but in most cases some
testing, adjustment, or other postupgrade administration is needed.
Please plan accordingly when upgrading to a new version.
@@ -44,11 +43,14 @@
brain work. These packages appear in the UPD (update) subdirectory of
a release after the delivery date.
- Importantly, the extent of security engineering advances with each
- new OpenPKG release. This means that security advisories and their
- associated UPD packages are only issued for the latest OpenPKG release
- and its immediate predecessor. Continuing to run outdated release
- packages not within the aforementioned security range introduces risks.
+ o The extent of security engineering advances with each new OpenPKG
+ release. This means that security advisories and their associated
+ UPD packages are only issued for the latest OpenPKG release and its
+ immediate predecessor. For example, just after OpenPKG released
+ version 2.2, security advisories were being issued for versions 2.1
+ and 2.2 only (version 2.0 reached end of life). Continuing to run
+ outdated release packages not within the aforementioned security
+ range introduces risks.
New in OpenPKG 2.1
==================
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
