<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -56,7 +56,7 @@ These releases will contain new features, improvements to existing features, and
 such. A minor release may deprecate certain features from previous releases. If a
 feature in version ``A.B`` is deprecated, it will continue to work in version
 ``A.B+1``. In version ``A.B+2``, use of the feature will raise a
-``PendingDeprecationWarning`` but will continue to work. Version ``A.B+3`` will
+``DeprecationWarning`` but will continue to work. Version ``A.B+3`` will
 remove the feature entirely.
 
 So, for example, if we decided to remove a function that existed in Django 1.0:</diff>
      <filename>docs/internals/release-process.txt</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>3bd384430ef7d6f2245db0bf2ffa2339410b1fe9</id>
    </parent>
  </parents>
  <author>
    <name>lukeplant</name>
    <email>lukeplant@bcc190cf-cafb-0310-a4f2-bffc1f526a37</email>
  </author>
  <url>http://github.com/mrts/django/commit/374e10db12ff6f86da5a0d9ccb65ea7e0d1d513b</url>
  <id>374e10db12ff6f86da5a0d9ccb65ea7e0d1d513b</id>
  <committed-date>2009-10-24T07:10:00-07:00</committed-date>
  <authored-date>2009-10-24T07:10:00-07:00</authored-date>
  <message>Fixed small error in deprecation policy.



git-svn-id: http://code.djangoproject.com/svn/django/trunk@11652 bcc190cf-cafb-0310-a4f2-bffc1f526a37</message>
  <tree>a7a1d6700aa7c2e869de7da7cba72ceeb5d2801c</tree>
  <committer>
    <name>lukeplant</name>
    <email>lukeplant@bcc190cf-cafb-0310-a4f2-bffc1f526a37</email>
  </committer>
</commit>
