summaryrefslogtreecommitdiffstats
path: root/ReleaseNotes.htm
diff options
context:
space:
mode:
authorkumpf <kumpf>2008-12-16 18:55:33 +0000
committerkumpf <kumpf>2008-12-16 18:55:33 +0000
commit5e6009db97c1a33f0a482e988571596915d6657e (patch)
treebf9122d7fe0f55b1f1c934623bb31b1307465a8c /ReleaseNotes.htm
parenta856bf03f37d804b3f32659c838ad8e2402efb14 (diff)
downloadtog-pegasus-5e6009db97c1a33f0a482e988571596915d6657e.zip
tog-pegasus-5e6009db97c1a33f0a482e988571596915d6657e.tar.gz
tog-pegasus-5e6009db97c1a33f0a482e988571596915d6657e.tar.xz
BUG#: 8273
TITLE: Remove trailing space characters DESCRIPTION: Remove meaningless whitespace.
Diffstat (limited to 'ReleaseNotes.htm')
-rw-r--r--ReleaseNotes.htm260
1 files changed, 130 insertions, 130 deletions
diff --git a/ReleaseNotes.htm b/ReleaseNotes.htm
index 0159421..854aebd 100644
--- a/ReleaseNotes.htm
+++ b/ReleaseNotes.htm
@@ -1036,25 +1036,25 @@ Notes for OpenPegasus 2.8.0</p>
<tr style="">
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27">
-
+
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p>&nbsp;</o:p></span></b></p>
</td>
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27">
-
+
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p>&nbsp;</o:p></span></b></p>
</td>
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27">
-
+
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p>&nbsp;</o:p></span></b></p>
</td>
<td style="padding: 0.75pt; background: rgb(202, 230, 202) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;" height="27">
-
+
<p class="MsoNormal" style="text-align: center;" align="center"><b><span style="font-family: Arial; color: black;"><o:p>&nbsp;</o:p></span></b></p>
</td>
@@ -1064,27 +1064,27 @@ Notes for OpenPegasus 2.8.0</p>
<tr style="">
<td style="padding: 0.75pt;" height="22">
-
+
<p class="MsoNormal" style="text-align: center;" align="center"><span style="font-family: Arial; color: black;"><font size="2">&nbsp;1.0</font><o:p></o:p></span></p>
</td>
<td style="padding: 0.75pt;" align="left" height="22">
-
+
<p class="MsoNormal" style="text-align: center;" align="center">
<font size="2"><span style="font-family: Arial">21 June 2008</span></font></p>
</td>
<td style="padding: 0.75pt;" align="left" height="22">
-
+
<p class="MsoNormal" style="text-align: center;" align="center">
<span style="font-family: Arial;"><font size="2">Karl Schopmeyer</font></span></p>
</td>
<td style="padding: 0.75pt;" height="22">
-
+
<p class="MsoNormal"><span style="font-family: Arial; color: black;"><font size="2">Initial
Submission</font><o:p><font size="2">
</font></o:p></span></p>
@@ -1113,7 +1113,7 @@ Submission</font><o:p><font size="2">
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer</td>
- <td style="padding: 0.75pt;" height="21">Incorporate All Comments to date
+ <td style="padding: 0.75pt;" height="21">Incorporate All Comments to date
(See discussion for list of changes)</td>
</tr>
@@ -1126,7 +1126,7 @@ Submission</font><o:p><font size="2">
<td style="padding: 0.75pt;" align="center" height="21">Karl Schopmeyer</td>
- <td style="padding: 0.75pt;" height="21">Add bug 7501 to compatibility
+ <td style="padding: 0.75pt;" height="21">Add bug 7501 to compatibility
issues table. Remove temp change list section</td>
</tr>
@@ -1143,7 +1143,7 @@ Submission</font><o:p><font size="2">
</tr>
-
+
</tbody>
</table>
@@ -1212,24 +1212,24 @@ tree.</p>
<div class="Section1">
<h2><span style="color: black;">OpenPegasus Functionality for This Release</span></h2>
-Pegasus overall status by release is defined by&nbsp; a
-<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a>
-that is available on the OpenPegasus web site .&nbsp; That web page shows the
-Pegasus users and developers the status of the various features found in Pegasus
-using a simple color coded key (white, red, yellow, green) and a description of
-each feature.<p>Pegasus 2.8.0
-is a major release, extending the previous Pegasus release in selected
-areas as described in the Pegasus&nbsp; PEP defining this release
+Pegasus overall status by release is defined by&nbsp; a
+<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a>
+that is available on the OpenPegasus web site .&nbsp; That web page shows the
+Pegasus users and developers the status of the various features found in Pegasus
+using a simple color coded key (white, red, yellow, green) and a description of
+each feature.<p>Pegasus 2.8.0
+is a major release, extending the previous Pegasus release in selected
+areas as described in the Pegasus&nbsp; PEP defining this release
.&nbsp; </p>
-<p>The major areas of development for this release&nbsp; were as follows. For
+<p>The major areas of development for this release&nbsp; were as follows. For
more information access the PEP for each change defined:</p>
- <p style="margin-top: 0pt; margin-bottom: 0pt;" align="left">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<font size="4">&nbsp;&nbsp;&nbsp;
+ <p style="margin-top: 0pt; margin-bottom: 0pt;" align="left">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<font size="4">&nbsp;&nbsp;&nbsp;
Table of Major Changes for this Release</font></p>
-
-
- <TABLE style="FONT-FAMILY: Arial" cellSpacing=1 borderColorDark=#666666
+
+
+ <TABLE style="FONT-FAMILY: Arial" cellSpacing=1 borderColorDark=#666666
borderColorLight=#CCCCCC border=1 width="82%">
<TBODY>
<TR align="center">
@@ -1283,7 +1283,7 @@ more information access the PEP for each change defined:</p>
</TR>
<TR align="center">
<TD width="7%">323</TD>
- <TD align="left" width="75%">DMTf Indication Profile Implementation, Stage
+ <TD align="left" width="75%">DMTf Indication Profile Implementation, Stage
1 (DMTF DSP 1054)</TD>
<TD width="128">
<a href="https://www.openpegasus.org/pp/uploads/40/16770/PEP323_DMTF_Indication_Profile_stage_1.htm">
@@ -1299,19 +1299,19 @@ more information access the PEP for each change defined:</p>
</TBODY>
</TABLE>
</html>
-<p>The status of several components of Pegasus functionality change status
-between Pegasus versions. <span class="norm"><a name="comtag_116">Features that
-have changed status can be identified by a change in color from the previous
-release to this release</a></span> on the
+<p>The status of several components of Pegasus functionality change status
+between Pegasus versions. <span class="norm"><a name="comtag_116">Features that
+have changed status can be identified by a change in color from the previous
+release to this release</a></span> on the
<a href="http://www.openpegasus.org/page.tpl?ggid=799">Feature Status WEB Page</a>.</p>
-<p>Finally, a significant number of internal changes and corrections were made
-under the control of the Pegasus bugzilla bug system. See the bug section below
+<p>Finally, a significant number of internal changes and corrections were made
+under the control of the Pegasus bugzilla bug system. See the bug section below
for more information.</p>
<h3><font color="#000000">Information on&nbsp; IPv6 Support (PEP 291)</font></h3>
-<p><b>NOTE:</b> This functionality was incorporated in OpenPegasus 2.7.0 but it
-was felt that the information below was worth repeating in the 2.8.0 Release
+<p><b>NOTE:</b> This functionality was incorporated in OpenPegasus 2.7.0 but it
+was felt that the information below was worth repeating in the 2.8.0 Release
Notes</p>
<p style="color: rgb(153, 51, 153);"><font color="#000000">IPv6 is short for "Internet
Protocol
@@ -1322,7 +1322,7 @@ to replace the current version Internet Protocol, IP Version 4
<font color="#3333FF">PEP
291</font></a><font color="#000000">.</font></p>
<p>The IPv6 support in OpenPegasus is
-controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for this
+controlled by the PEGASUS_ENABLE_IPV6 build variable. The default for this
variable is &quot;true&quot;; setting this to
'false' before building OpenPegasus will disable the IPv6 support.<br>
</p>
@@ -1386,7 +1386,7 @@ kernel supports IPv6, take a look into your /proc filesystem. The entry
/proc/net/if_inet6 &amp;&amp; echo "Running kernel is IPv6 ready"</font></div>
<p>For more information on
enabling
-IPv6 in the Linux kernel and configuring network interfaces, refer to
+IPv6 in the Linux kernel and configuring network interfaces, refer to
<a
href="http://tldp.org/HOWTO/html_single/Linux+IPv6-HOWTO/">The Linux
Documentation Project's IPv6 HOWTO</a>.<br>
@@ -1406,8 +1406,8 @@ and<span
href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248052">RedHat
bug 248052</a>,
</span>
-and manifests itself as an intermittent IPv6 socket failure. You should be aware
-that OpenPegasus with IPv6 enabled may be significantly impacted in these
+and manifests itself as an intermittent IPv6 socket failure. You should be aware
+that OpenPegasus with IPv6 enabled may be significantly impacted in these
environments.</p>
<h4><font color="#000000">IPv6 on Windows</font></h4>
<p>Microsoft provides supported IPv6
@@ -1429,7 +1429,7 @@ on Windows Vista or Windows Server 2008.<br>
<br>
For more information on
installing, configuring, and using IPv6 on Windows platforms, refer to
-the document
+the document
<a
href="https://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx">
<font color="#000000">IPv6
@@ -1450,16 +1450,16 @@ running on the WBEM standard http port of 5988:<br>
<div style="margin-left: 40px;"><br>
osinfo -h ::1</div>
<h2><a name="Compatibility_Considerations_">Compatibility Considerations</a></h2>
-<p>Support for forward-compatibility is a fundamental design principle for the
-OpenPegasus project. As a Community, our goal is for well-behaved OpenPegasus
-Providers or Clients, using only the externally defined OpenPegasus interface,
-to continue to work with a minor version upgrade of OpenPegasus. However, there
-are certain classes of errors (e.g., non-compliance with a standard that
-significantly affects interoperability) that may require the Community to make
-potentially incompatible changes. The following table contains a list of defect
-fixes that MAY impact, even well-behaved, OpenPegasus Providers or Clients when
+<p>Support for forward-compatibility is a fundamental design principle for the
+OpenPegasus project. As a Community, our goal is for well-behaved OpenPegasus
+Providers or Clients, using only the externally defined OpenPegasus interface,
+to continue to work with a minor version upgrade of OpenPegasus. However, there
+are certain classes of errors (e.g., non-compliance with a standard that
+significantly affects interoperability) that may require the Community to make
+potentially incompatible changes. The following table contains a list of defect
+fixes that MAY impact, even well-behaved, OpenPegasus Providers or Clients when
upgrading to OpenPegasus 2.8.0.</p>
- <TABLE style="FONT-FAMILY: Arial" cellSpacing=1 borderColorDark=#666666
+ <TABLE style="FONT-FAMILY: Arial" cellSpacing=1 borderColorDark=#666666
borderColorLight=#CCCCCC border=1 width="80%">
<TBODY>
<TR align="center">
@@ -1468,14 +1468,14 @@ upgrading to OpenPegasus 2.8.0.</p>
</TR>
<TR align="center">
<TD><a href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=6812">6812</a></TD>
- <TD align="left">In Pegasus 2.8, the behavior of the setName() method is
- changed in the Pegasus C++ interface for the CIM data type model. For
- data types that use a shared representation model, the setName() method
- now throws an Exception when the object is &quot;contained&quot; by another CIM
+ <TD align="left">In Pegasus 2.8, the behavior of the setName() method is
+ changed in the Pegasus C++ interface for the CIM data type model. For
+ data types that use a shared representation model, the setName() method
+ now throws an Exception when the object is &quot;contained&quot; by another CIM
data object. <br>
Specifically, setName() may throw the new exception in these cases: <br>
<u>CIMProperty</u> contained by CIMClass, CIMInstance, and CIMObject <br>
- <u>CIMQualifier</u> contained by CIMClass, CIMInstance, CIMObject,
+ <u>CIMQualifier</u> contained by CIMClass, CIMInstance, CIMObject,
CIMProperty, CIMParameter, and CIMMethod <br>
<u>CIMMethod</u> contained by CIMClass <br>
<u>CIMParameter</u> contained by CIMMethod</TD>
@@ -1483,56 +1483,56 @@ upgrading to OpenPegasus 2.8.0.</p>
<TR align="center">
<TD><a href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=7453">7453</a></TD>
<TD>
- <p align="left">In Pegasus 2.8, the C++ CMPI IndicationMI function
+ <p align="left">In Pegasus 2.8, the C++ CMPI IndicationMI function
signatures have been changed to fit the CMPIIndicationMIFT definitions.
<br>
- The CmpiResult parameter in CmpiIndicationMI authorizeFilter, mustPoll,
- activateFilter and deActivateFilter have been removed cause it does not
+ The CmpiResult parameter in CmpiIndicationMI authorizeFilter, mustPoll,
+ activateFilter and deActivateFilter have been removed cause it does not
exist in the CMPIIndicationMIFT definitions. <br>
- The missing CmpiContext parameter and CMPIStatus have been added to
+ The missing CmpiContext parameter and CMPIStatus have been added to
enableIndications and disableIndications.</TD>
</TR>
<TR align="center">
<TD><a href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=7488">7488</a></TD>
<TD>
- <p align="left">In Pegasus 2.8, the CMPI property filter handling has
+ <p align="left">In Pegasus 2.8, the CMPI property filter handling has
been improved in performance. <br>
- Two things have changed in the behaviour of the property filter
+ Two things have changed in the behaviour of the property filter
handling: <br>
- * Repeated applying of property filters onto the same instance will now
- only leave the properties which build the most common dominator on the
+ * Repeated applying of property filters onto the same instance will now
+ only leave the properties which build the most common dominator on the
instance. <br>
- * It is not possible anymore to add properties not defined for the
+ * It is not possible anymore to add properties not defined for the
corresponding class to an instance.</TD>
</TR>
<TR align="center">
<TD><a href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=7624">7624</a></TD>
<TD>
- <p align="left">In Pegasus 2.8, the algorithm used by the MessageLoader
- to search the accept language list to determine which message file to
- open was changed. Before Pegasus 2.8, the Message Loader used the
+ <p align="left">In Pegasus 2.8, the algorithm used by the MessageLoader
+ to search the accept language list to determine which message file to
+ open was changed. Before Pegasus 2.8, the Message Loader used the
following algorithm: </p>
<blockquote>
- <p align="left">1.) The Message Loader will search the accept
- language list for an exact match. The first exact match found will
+ <p align="left">1.) The Message Loader will search the accept
+ language list for an exact match. The first exact match found will
be returned.<br>
- 2.) If an exact match does not exist, the Message Loader will return
+ 2.) If an exact match does not exist, the Message Loader will return
an ICU &quot;fallback&quot; match for the first entry in accept language list.<br>
- 3.) If an ICU &quot;fallback&quot; match does not exist for the first entry,
+ 3.) If an ICU &quot;fallback&quot; match does not exist for the first entry,
it will return the ROOT resource bundle.</p>
</blockquote>
- <p align="left">With the release of Pegasus 2.8, the Message Loader will
- not longer return ICU &quot;fallback&quot; matches. In addition, it will give
- preference to the default process locale over the ROOT resource bundle.
- In Pegasus 2.8, the Message Loader has been modified to use the
+ <p align="left">With the release of Pegasus 2.8, the Message Loader will
+ not longer return ICU &quot;fallback&quot; matches. In addition, it will give
+ preference to the default process locale over the ROOT resource bundle.
+ In Pegasus 2.8, the Message Loader has been modified to use the
following algorithm: </p>
<ul>
- <p align="left">1.) The Message Loader will search the accept
- language list for an exact match. The first exact match found will
+ <p align="left">1.) The Message Loader will search the accept
+ language list for an exact match. The first exact match found will
be returned.<br>
- 2.) If an exact match does not exist, the Message Loader will return
+ 2.) If an exact match does not exist, the Message Loader will return
an exact match for the default process locale.<br>
- 3.) If an exact match for the default process locale is not found,
+ 3.) If an exact match for the default process locale is not found,
it will return the ROOT resource bundle.</p>
</ul>
</TD>
@@ -1541,16 +1541,16 @@ upgrading to OpenPegasus 2.8.0.</p>
<TD><a href="http://cvs.rdg.opengroup.org/bugzilla/show_bug.cgi?id=7501">
7501</a></TD>
<TD>
- <p align="left">Since OpenPegasus 2.7.2 the way CMPI_chars are added to
- arrays was corrected to follow the CMPI specification. Following the
- CMPI specification means that CMPI_chars are not to be dereferenced,
+ <p align="left">Since OpenPegasus 2.7.2 the way CMPI_chars are added to
+ arrays was corrected to follow the CMPI specification. Following the
+ CMPI specification means that CMPI_chars are not to be dereferenced,
contrary to all other subtypes of CMPIValues.<br>
- If you experience an error since switching over to OpenPegasus 2.8
- saying &quot;The byte sequence starting at offset xx is not valid UTF-8
- encoding&quot;, this is an indication for a missing update in the provider
+ If you experience an error since switching over to OpenPegasus 2.8
+ saying &quot;The byte sequence starting at offset xx is not valid UTF-8
+ encoding&quot;, this is an indication for a missing update in the provider
code.<br>
<br>
- The update for a C CMPI provider using arrays of CMPI_chars is to use a
+ The update for a C CMPI provider using arrays of CMPI_chars is to use a
char* now as input parameter instead of a char**.<br>
<u>CMPI Example:</u><br>
&nbsp;&nbsp;&nbsp; char* role = &quot;Unknown&quot;;<br>
@@ -1627,7 +1627,7 @@ Servers and means that the the provider qualifier is unused in Pegasus.</li>
indications and lifecycle indications when defined specifically by
providers. Pegasus does not support lifecycle indications if they are
not defined by the provider or for changes to CIM Classes.<font
- color="#ff0000"> </font><span class="norm"><font color="#ff0000">&nbsp;</font>For
+ color="#ff0000"> </font><span class="norm"><font color="#ff0000">&nbsp;</font>For
more information see the Pegasus CVS file:<a name="comtag_137"><font size="2">
</font><font
face="Courier New" size="2">&nbsp;pegasus/src/Unsupported/LifecycleIndicationProvider/README.LifecycleIndications.htm</font></a><font size="2">.</font></span></li>
@@ -1672,32 +1672,32 @@ Pegasus compiler does not support the namespace pragma.</p>
</li>
<li><b>CIMOperation Trailer </b>- Pegasus implements
chunking
-based on the DSP0200 1.2.0 preliminary spec. including the operation trailer
+based on the DSP0200 1.2.0 preliminary spec. including the operation trailer
defined in that specification Refer to bug
<a
- href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6760">6760</a> for more details.
- This trailer was completely removed from the DSP0200 1.2 final specification
- as a non-compatible change so that if chunking is used Pegasus is returning
+ href="http://cvs.opengroup.org/bugzilla/show_bug.cgi?id=6760">6760</a> for more details.
+ This trailer was completely removed from the DSP0200 1.2 final specification
+ as a non-compatible change so that if chunking is used Pegasus is returning
a noncompliant response to enumerate type requests. <br>
</li>
</ol>
<h2><b><span style="font-family: Times;">OpenPegasus <a
name="Supported Platforms">Supported
Platforms</a></span></b></h2>
-<p align="left">Each OpenPegasus release lists as 'active' platforms those
-hardware/software platforms that have recognized ports for the Pegasus code base
-including a maintainer for the platform that will be willing to regularly
-document issues and/or fix defects as the Pegasus code base is changed.&nbsp;
-Pegasus may be operable on other platforms (ex. Windows 98) but without a group
-to provide the role of test and maintenance, correct operation of&nbsp; Pegasus
-cannot be assured.&nbsp; In all cases, including the active platforms, it is the
-responsibility of the entity that packages and/or compiles OpenPegasus for
-shipment or deployment, to read, and actively monitor the Pegasus bugzilla
-database for a list of relevant defects that affect their platform.&nbsp;&nbsp;
-The platforms that are considered ported are shown in the two tables below.&nbsp;
-The first table represents platform sofr which testing is done on a regular
-basis and reported to the Pegasus Nightly Build Test WEB Page. Those platforms
-which have been ported but do not have test results that are current at the time
+<p align="left">Each OpenPegasus release lists as 'active' platforms those
+hardware/software platforms that have recognized ports for the Pegasus code base
+including a maintainer for the platform that will be willing to regularly
+document issues and/or fix defects as the Pegasus code base is changed.&nbsp;
+Pegasus may be operable on other platforms (ex. Windows 98) but without a group
+to provide the role of test and maintenance, correct operation of&nbsp; Pegasus
+cannot be assured.&nbsp; In all cases, including the active platforms, it is the
+responsibility of the entity that packages and/or compiles OpenPegasus for
+shipment or deployment, to read, and actively monitor the Pegasus bugzilla
+database for a list of relevant defects that affect their platform.&nbsp;&nbsp;
+The platforms that are considered ported are shown in the two tables below.&nbsp;
+The first table represents platform sofr which testing is done on a regular
+basis and reported to the Pegasus Nightly Build Test WEB Page. Those platforms
+which have been ported but do not have test results that are current at the time
of the release are reported in the second table</p>
<p align="center"><br>
<b>Actively Supported Platforms (Nightly Tests Reported for this release</b></p>
@@ -1780,14 +1780,14 @@ OS</span></b><span style="color: black;"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: black;">Windows 2000</span></p>
</td>
<td style="padding: 0.75pt; ">
- <font size="3">Microsoft Visual C++ Ver.&nbsp; 6 and Microsoft .Net compiler version.&nbsp;Works on VC .NET 2003 v7.1).
+ <font size="3">Microsoft Visual C++ Ver.&nbsp; 6 and Microsoft .Net compiler version.&nbsp;Works on VC .NET 2003 v7.1).
NOTE: Visual C++ Ver. 6 no longer being regularly tested.</font></td>
</tr>
<tr>
<td style="padding: 0.75pt; "> <font size="3">Windows 2003</span></font></p>
</td>
<td style="padding: 0.75pt; ">
- <font size="3">Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1.
+ <font size="3">Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1.
Note: Visual C++ Ver. 6 no longer being regular tested.
</font>
</td>
@@ -1803,18 +1803,18 @@ Alpha</font></big></td>
<td style="vertical-align: top;"><big><span class="norm"></span><font
style="color: rgb(0, 0, 0);"> HP OpenVMS 8.3 or later IA64</font></big></td>
<td style="vertical-align: top;"><span class="norm"></span><big><font
- style="color: rgb(0, 0, 0);">HP C++ V7.</font><font color="#993399">3-023 or
+ style="color: rgb(0, 0, 0);">HP C++ V7.</font><font color="#993399">3-023 or
later required</font><font
style="color: rgb(0, 0, 0);"> on OpenVMS IA64</font></big></td>
</tr>
<tr>
<td style="vertical-align: top;"><font size="3">z/OS V1.7 and up</font></td>
- <td style="vertical-align: top;"><font size="3">XL C/C++ from z/OS Version
+ <td style="vertical-align: top;"><font size="3">XL C/C++ from z/OS Version
1.7 and up</font></td>
</tr>
</tbody>
</table>
-&nbsp;<p align="center"><b>Platforms no Actively supported for this release (No
+&nbsp;<p align="center"><b>Platforms no Actively supported for this release (No
current Nightly Build Test Results</b></p>
<table class="MsoNormalTable" style="width: 90%;" border="1"
cellpadding="0" cellspacing="1" id="table2">
@@ -1837,7 +1837,7 @@ OS</span></b><span style="color: black;"><o:p></o:p></span></p>
<td style="padding: 0.75pt; "> <font size="3">Windows XP</font></p>
</td>
<td style="padding: 0.75pt; ">
- <font size="3">Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1.
+ <font size="3">Microsoft Visual C++ Ver. 6 and Microsoft .Net compiler Version 7.1.
Note: Visual C++ Ver. 6 no longer being regular tested.
</font>
</td>
@@ -1876,13 +1876,13 @@ patches Pegasus requires.</font></p>
style="color: rgb(0, 0, 0);">RHAS
2.1 needs the update to fix Red Hat Bugzilla 98815.</font></p></li>
<li>
- <p style="margin-top: 0pt; margin-bottom: 0pt;">RHEL 4.4 multithreading bug in
-getpwuid-r could cause a CIM Server failure (Bugzilla 6232). This is fixed in
+ <p style="margin-top: 0pt; margin-bottom: 0pt;">RHEL 4.4 multithreading bug in
+getpwuid-r could cause a CIM Server failure (Bugzilla 6232). This is fixed in
RHEL 4.5</p></li>
<li>
- <p style="margin-top: 0pt; margin-bottom: 0pt;">Red Hat and SUSE Linux
- multiple versions -
-multithreaded client intermittently fails connecting to IPv6 (Pegasus Bugzilla
+ <p style="margin-top: 0pt; margin-bottom: 0pt;">Red Hat and SUSE Linux
+ multiple versions -
+multithreaded client intermittently fails connecting to IPv6 (Pegasus Bugzilla
6586) (Red Hat bug 248052)<br></p></li>
</ol>
</div>
@@ -1899,23 +1899,23 @@ found at:
<h2><span style="color: black;"><a name="PEGASUS Bugs">Pegasus Defects</a></span></h2>
<p>The Pegasus bugzilla database documents any defects found in Pegasus
and&nbsp; is available through the following link:&nbsp; <a href="http://cvs.rdg.opengroup.org/bugzilla/">OpenPegasus bugzilla
-database</a>.&nbsp;&nbsp;
-Effective with the start of the Pegasus 2.6 work, all changes to the CVS tree
-were documented through bugs.&nbsp; Bugs reports were filed not only for bugs and
-their corresponding fixes but also as part of the process of committing new code
-representing the work on PEPs done for Pegasus 2.6 and all subsequent versions.&nbsp; Therefore, a search of
-the Open Pegasus bugzilla base for bugs with the tag for a particular version
+database</a>.&nbsp;&nbsp;
+Effective with the start of the Pegasus 2.6 work, all changes to the CVS tree
+were documented through bugs.&nbsp; Bugs reports were filed not only for bugs and
+their corresponding fixes but also as part of the process of committing new code
+representing the work on PEPs done for Pegasus 2.6 and all subsequent versions.&nbsp; Therefore, a search of
+the Open Pegasus bugzilla base for bugs with the tag for a particular version
(ex.&nbsp;
<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.0_APPROVED">
2.6.0_APPROVED</a>,
<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.6.1_APPROVED">
2.6.1_APPROVED</a>,
-<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.7.0_APPROVED">2.7.0_APPROVED</a>) will yield all changes to
+<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.7.0_APPROVED">2.7.0_APPROVED</a>) will yield all changes to
the Pegasus CVS tree for that Pegasus release.</p>
<p>
-&nbsp;&nbsp;&nbsp;&nbsp; - Changes for Pegasus 2.8.0 release (bugs Tagged
-2.8.0_APPROVED)&nbsp;<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.8.0_APPROVED">
+&nbsp;&nbsp;&nbsp;&nbsp; - Changes for Pegasus 2.8.0 release (bugs Tagged
+2.8.0_APPROVED)&nbsp;<a href="http://cvs.rdg.opengroup.org/bugzilla/buglist.cgi?keywords=2.8.0_APPROVED">
Pegasus 2.8.0_APPROVED bug list</a></p>
<h2><a
@@ -1936,10 +1936,10 @@ OpenPegasus Approved PEPs.</a></p>
<ol>
<li>
- PEP 333 - OpenPegasus Release Definition - </b>This PEP ( and a corresponding
+ PEP 333 - OpenPegasus Release Definition - </b>This PEP ( and a corresponding
section in the Pegasus wiki) is used
throughout the development of this version as the control point for
-functionality that will go into the release and points to all of the PEPs that
+functionality that will go into the release and points to all of the PEPs that
represent the Pegasus&nbsp; functionality changes for this version of Pegasus.</li>
<b>
@@ -1952,28 +1952,28 @@ Platforms</li>
<li>
<a href="http://www.openpegasus.org/pp/uploads/40/16780/PEP329_ExternalInterface2.8.htm">
- PEP 329</a> - OpenPegasus 2.8 External Interfaces - </b>Lists the public
- interfaces for clients and providers that are considered external and
+ PEP 329</a> - OpenPegasus 2.8 External Interfaces - </b>Lists the public
+ interfaces for clients and providers that are considered external and
therefore &quot;frozen&quot;.<b><br>
</li>
<li>
<a href="http://www.openpegasus.org/pp/uploads/40/16779/PEP330_SDKFile2.8.0.htm">
- PEP 330</a> - OpenPegasus&nbsp; SDK Packaging Definition - </b>Defines the
+ PEP 330</a> - OpenPegasus&nbsp; SDK Packaging Definition - </b>Defines the
recommended set of files for inclusion in the OpenPegasus SDK</li>
<b>
<li>
<a href="http://www.openpegasus.org/pp/uploads/40/16778/PEP331_RuntimePackaging2.8.0.htm">
- PEP 331</a> - Pegasus&nbsp; Runtime Packaging Definition - </b>Defines the
+ PEP 331</a> - Pegasus&nbsp; Runtime Packaging Definition - </b>Defines the
recommended set of files for inclusion in this OpenPegasus release.</li>
<b>
- <li>PEP 332 - Pegasus Release Notes (This document located in the
- approved PEP
+ <li>PEP 332 - Pegasus Release Notes (This document located in the
+ approved PEP
repository and the OpenPegasus source tree root directory) <br>
</li>