[release-notes: 5/5] Added the rewheel module to the Python release note.

[pbokoc]

commit 8ed32f4c58c60d578c4bf32df0b629558bb7a09d
Author: Barbora Ancincova <bancinco at redhat.com>
Date:   Thu Oct 16 14:44:21 2014 +0200

    Added the rewheel module to the Python release note.

 en-US/Development.xml |   37 +++++++++++++++++++++++++++++++++++++
 1 files changed, 37 insertions(+), 0 deletions(-)
---
diff --git a/en-US/Development.xml b/en-US/Development.xml
index d5cae46..d53ad8a 100644
--- a/en-US/Development.xml
+++ b/en-US/Development.xml
@@ -52,6 +52,43 @@
         While the majority of Python packages are available for both Python and Python3, the <emphasis>default</emphasis> implementation of Python in Fedora is Python 2.7
       </para>
     </note>
+    <bridgehead renderas="sect3">The rewheel module</bridgehead>
+    <para>
+	For version 3.4, Python upstream has decided to implement changes summarized in the <ulink url="http://legacy.python.org/dev/peps/pep-0453/">PEP 453</ulink> document. In short, these mean:
+</para>
+<orderedlist>
+	<listitem>
+		<para>
+			 bundling archives with the <systemitem>setuptools</systemitem> and <systemitem>pip</systemitem> utilities in Python distribution
+		</para>
+	</listitem>
+	<listitem>
+		<para>
+			providing the <systemitem>ensurepip</systemitem> module that is able to install these archives either on a system or in the <systemitem>virtualenv</systemitem> environment. 
+		</para>
+	</listitem>
+</orderedlist>
+<para>
+	Due to Fedora strict non-bundling policies, <systemitem>setuptools</systemitem> and <systemitem>pip</systemitem> are unbundled. To match the upstream functionality, the following approach has been implemented:
+</para>
+<orderedlist>
+	<listitem>
+		<para>
+			The <package>python3</package> package now depends on the <package>python3-setuptools</package> and <package>python3-pip</package>. This means that users do not have to use the <systemitem>ensurepip</systemitem> to install <systemitem>setuptools</systemitem> and <systemitem>pip</systemitem> utilities separately as they are by default installed altogether with <package>python3</package>
+		</para>
+	</listitem>
+	<listitem>
+		<para>
+			To install the <systemitem>setuptools</systemitem> and <systemitem>pip</systemitem> utilities in the <systemitem>virtualenv</systemitem> environment from the system packages, a mechanism called <systemitem>rewheel</systemitem> has been implemented to Fedora 21.  When a new <systemitem>virtualenv</systemitem> is being created, <systemitem>rewheel</systemitem> takes the system <package>python3-setuptools</package> and <package>python3-pip</package> packages, recreates their archives and installs them in the new <systemitem>virtualenv</systemitem> so that the upstream functionality is preserved.
+		</para>
+	</listitem>
+</orderedlist>
+<para>
+	One more advantage is provided by the <systemitem>rewheel</systemitem> approach. When there is a bug, for example a security issue, in either <package>python3-setuptools</package> or <package>python3-pip</package>, Fedora maintainers of these packages fix the bug and users get the fixed packages. Therefore, <systemitem>virtualenvs</systemitem> created after updating to fixed <package></package> or <package>python3-pip</package> will have already fixed version. With pure upstream Python, this approach is not possible, users will have to wait for upstream to release new Python version with these fixes incorporated. This means that the <systemitem>rewheel</systemitem> patch makes the <package>python3</package> package fulfill Fedora's high packaging standards and also helps to make <systemitem>virtualenvs</systemitem> more secure.
+</para>
+        <para>
+	    See the <ulink url="https://github.com/fedora-python/rewheel">Rewheel</ulink> page on GitHub for additional information about <systemitem>rewheel</systemitem>.
+        </para>
   </section>
 
    <section id="development-rpm">