Skip to content

Commit 0e5f76b

Browse files
committed
Cleaned document
Deleted outdated section, outcommented two other sections as currently not needed.
1 parent 80ba859 commit 0e5f76b

File tree

1 file changed

+2
-17
lines changed

1 file changed

+2
-17
lines changed

xml/MAIN-SBP-SUSE-security-report-2024.xml

Lines changed: 2 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@
144144

145145
</sect1>
146146

147-
<!--<sect1 xml:id="sec-background">
147+
<!-- <sect1 xml:id="sec-background">
148148
<title>Background</title>
149149
150150
<para>A modern Linux operating system, such as SUSE Linux Enterprise Server for enterprise use or
@@ -287,24 +287,9 @@
287287
</tgroup>
288288
</table>
289289
290-
</sect1>
291-
292-
<sect1 xml:id="sec-prefer-upgrades-over-backports">
293-
<title>When to prefer version upgrades over backports</title>
294-
295-
<para> It is a general policy rule that no new upstream versions of a package are introduced into
296-
our enterprise products. This rule is not an absolute rule however. For certain types of
297-
packages, in particular antivirus software, security concerns weigh heavier than the conservative
298-
approach that is preferable from the perspective of quality assurance. For packages in that
299-
class, occasionally newer versions are introduced to a released version of an enterprise product
300-
line. </para>
301-
302-
<para>Sometimes also for other package types the decision is made to introduce a new version
303-
instead of a backport. This happens when producing a backport is not economically feasible or
304-
if there is a very relevant technical reason for introducing the newer version.</para>
305-
306290
</sect1>-->
307291

292+
308293
<sect1 xml:id="sec-security-vulnerabilities-2024">
309294
<title>Major security vulnerabilities in 2024</title>
310295

0 commit comments

Comments
 (0)