From f8af503e6a7c1dc7209d01d6c48e0fb8f0737985 Mon Sep 17 00:00:00 2001
From: Warren Block <wblock@FreeBSD.org>
Date: Mon, 14 Jul 2014 02:27:10 +0000
Subject: [PATCH] Fix lists in the Python section.
---
.../news/status/report-2014-04-2014-06.xml | 22 +++++++++----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml
index af1120f3b8..ab8931a344 100644
--- a/en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml
+++ b/en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml
@@ -475,7 +475,7 @@
<body>
<p>
- <li><p>We are pleased to announce the availability of conflict-free
+ <p>We are pleased to announce the availability of conflict-free
Python package support across different Python versions based on the
USES=uniquefiles feature recently introduced to the Ports framework.
A Python package can be marked as buildable and installable in
@@ -483,27 +483,27 @@
host. The package building tools, however, do not support this feature
yet and the Python team will work closely with portmgr and pkg
developers to enable support on a global ports and package scale.
- </p></li>
+ </p>
- <li><p>In May and June a huge clean-up operation took place to remove
+ <p>In May and June a huge clean-up operation took place to remove
the last bits and pieces targeting easy_install. In the beginning of
July we committed the final changes to remove easy_install support
completely from the ports framework. This greatly simplifies the
infrastructure and allows us to modernize and maintain it with less
- effort.</p></li>
+ effort.</p>
- <li><p>We added Python 3.4, removed Python 3.1 after its end of life,
+ <p>We added Python 3.4, removed Python 3.1 after its end of life,
updated the setuptools ports to version 5.1 and PyPy's development
version to 2.3.1. The latest Python 2.7.8 and an updated setuptools
- will hit the tree shortly.</p></li>
+ will hit the tree shortly.</p>
- <li><p>Our upstreaming effort continues to produce good outcomes for
- simplifying maintenance and reducing complexity.</p></li>
+ <p>Our upstreaming effort continues to produce good outcomes for
+ simplifying maintenance and reducing complexity.</p>
- <li><p>Looking forward, one of the top priorities is to comply with
+ <p>Looking forward, one of the top priorities is to comply with
the USES framework in the foreseeable future and to roll out a
consistent maintainer policy for integrating new Python-related ports
- into the tree.</p></li>
+ into the tree.</p>
</p>
</body>
@@ -518,7 +518,7 @@
regression-test, etc.)</task>
<task>More tasks can be found on the team's wiki page (see links).</task>
<task>To get involved, interested people can say hello on IRC and let us
- know their areas of interes!</task>
+ know their areas of interest!</task>
</help>
</project>