From 42142214c4b00863ff2c0142a09d467a67452cf7 Mon Sep 17 00:00:00 2001
From: holgerd77 <Holger.Drewes@googlemail.com>
Date: Thu, 27 Aug 2015 16:27:09 +0200
Subject: [PATCH] Release commit for v.0.7.0

---
 README.rst           | 14 ++------------
 docs/developers.rst  |  7 ++++---
 requirements_dev.txt |  2 +-
 3 files changed, 7 insertions(+), 16 deletions(-)

diff --git a/README.rst b/README.rst
index 4ba6b5c..07089c3 100644
--- a/README.rst
+++ b/README.rst
@@ -2,18 +2,8 @@
 django-public-project
 =====================
 
-Django Public Project (DPP) is a content management system tailored to represent and expose the various
-structural parts and participants in big projects and picture the inderdependencies between them.
-
-DPP can be used by civic transparency groups or governmental institutions to monitor or inform about 
-big publicly funded projects for
-helping the public to easier follow the progress of the project and get a deeper understanding of what
-is going on, who is acting/involved and how the project goals changed over time. 
-
-DPP is not self-installable but comes as a Django app, so it needs some development work to be integrated
-inside a Django project. Nevertheless it comes with a predefined site layout tailored to the domain described
-above and a Django admin integration to enter all the data about project parts, participants and events occured,
-so after a quick initial installation and deployment it can be used and updated by non-technical folks.
+Django Public Project (DPP) is a custom CMS for making large public projects, political processes and enquiry commissions
+more transparent.
 
 Current languages available: EN | DE
 
diff --git a/docs/developers.rst b/docs/developers.rst
index 11fa36d..8dcd3f2 100644
--- a/docs/developers.rst
+++ b/docs/developers.rst
@@ -10,8 +10,8 @@ Running the Test Suite
 Tests for ``DPP`` are organized in an own django project called ``bpw_tests`` located under the
 folder ``tests``. For running the test suite the following libraries are required:
 
-* `Selenium <http://selenium-python.readthedocs.org/en/latest/>`_ 2.3+
-* `django-dynamic-fixture <https://github.com/paulocheque/django-dynamic-fixture>`_ 1.6+
+* `Selenium <http://selenium-python.readthedocs.org/en/latest/>`_ 2.45+
+* `django-dynamic-fixture <https://github.com/paulocheque/django-dynamic-fixture>`_ 1.8+
 
 The following types of tests are implemented:
 
@@ -105,7 +105,7 @@ Then translate the missing identifier strings and compile the message files with
 
 Release Notes
 =============
-**Changes in version 0.7.0-beta** (Not yet released)
+**Changes in version 0.7.0-beta** (2015-08-27)
 
 * Support for ``Django 1.8`` (support for older versions dropped)
 * Switched to ``Django`` internal migrations. South dependencies are removed, but you can still find the
@@ -114,6 +114,7 @@ Release Notes
   latest ``0.6`` release first and run the ``migrate`` command within ``South`` context before switching
   to this release. Then from ``0.7`` run the ``migrate`` command with the ``--fake-initial`` flag: ``python manage.py migrate --fake-initial``.
 * Updated requirements of various library dependencies
+* Fixed a bug for document comments
 
 **Changes in version 0.6.3-beta** (2014-12-08)
 
diff --git a/requirements_dev.txt b/requirements_dev.txt
index b296eb8..5542e14 100644
--- a/requirements_dev.txt
+++ b/requirements_dev.txt
@@ -1,4 +1,4 @@
 Sphinx>=1.3
 selenium>=2.45
-django-dynamic-fixture>=1.8.4
+django-dynamic-fixture>=1.8
 ipython