<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -1,6 +1,6 @@
-===============
+###############
 django-oopviews
-===============
+###############
 
 .. contents::
 
@@ -79,3 +79,16 @@ will take the first element of that tuple as a priority value similar to the
 one used in the &quot;Accept&quot;-handling. This way, you can prioritize methods for 
 the case, that the user requests any type of a given family like for instance
 'text/\*'.
+
+History
+========
+
+0.2 (Oct 1 2008)
+    comes as its own library using setuptools and offering with the 
+    django_oopviews.ctn module a simple implementation of content negotiation
+    in HTTP using OOPViews.
+    
+0.1 (inofficial)
+    This version only included the BaseView as well as the create_view 
+    function and was bundled with the django-zsutils library.
+    </diff>
      <filename>README.rst</filename>
    </modified>
    <modified>
      <diff>@@ -1,4 +1,4 @@
-VERSION = (0, 2, 0, 'beta', 0)
+VERSION = (0, 2, 0, 'final', 0)
 
 def get_version():
     v = &quot;%d.%d.%d&quot; % VERSION[:3]</diff>
      <filename>django_oopviews/__init__.py</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>f7dde62936843049605c490c26614290e27c8109</id>
    </parent>
  </parents>
  <author>
    <name>Horst Gutmann</name>
    <email>zerok@zerokspot.com</email>
  </author>
  <url>http://github.com/zerok/django-oopviews/commit/2ed44332279daefbae0804f9f060901c38ff34cd</url>
  <id>2ed44332279daefbae0804f9f060901c38ff34cd</id>
  <committed-date>2008-10-01T11:19:05-07:00</committed-date>
  <authored-date>2008-10-01T11:19:05-07:00</authored-date>
  <message>Added some versioning history and changed the version number to 0.2.0</message>
  <tree>e9db7613dbeb6d1004d2b0de2fa5c021ba4de7c4</tree>
  <committer>
    <name>Horst Gutmann</name>
    <email>zerok@zerokspot.com</email>
  </committer>
</commit>
