Updated docs.

alixedi · Jun 4, 2014 · 73e2581 · 73e2581
1 parent c1f3a1a
commit 73e2581
Show file tree

Hide file tree

Showing 3 changed files with 17 additions and 7 deletions.
diff --git a/HISTORY.rst b/HISTORY.rst
@@ -3,10 +3,16 @@
 History
 -------
 
-0.1.0 (2014)
+i.0.0 (2014)
+++++++++++++
+
+* Got to 93% test coverage. 
+
+
+0.3.0 (2014)
 ++++++++++++++++++
 
-* First release on PyPI.
+* Changed the mapping from User to Group, dealt with self-referencing models etc.
 
 
 0.2.0 (2014)
@@ -15,8 +21,11 @@ History
 * Added support for ManyToMany fields in SIEVE_MODEL
 
 
-
-0.3.0 (2014)
+0.1.0 (2014)
 ++++++++++++++++++
 
-* Changed the mapping from User to Group, dealt with self-referencing models etc.
+* First release on PyPI.
+
+
+
+
diff --git a/README.rst b/README.rst
@@ -12,7 +12,8 @@ django_sieve
         :target: https://crate.io/packages/django_sieve?version=latest
 
 
-Filter user-data based on multiple criteria.
+For a lot of web applications - Blogs come to mind as a canonical example, the queryset needs to be filtered in the views based upon some business rules. For instance, in a Blog, a "Dashboard" view - allowing editing of posts, should only ever have posts written by the user who is currently logged-in.
+In general, there is a need to filter data based on some business logic - universally! i.e. across each and every view. The ugly way of doing this would be to write queries substantiating the business logic in every single view. Sieve does the same job beautifully, minimally and correctly.
 
 Installation
 ------------

diff --git a/sieve/__init__.py b/sieve/__init__.py
@@ -1 +1 @@
-__version__ = '0.3.0'
+__version__ = '1.0.0'