increment version number

chfw · chfw · commit 865cfe03037c · 2017-06-28T17:35:40.000+01:00
diff --git a/README.rst b/README.rst
@@ -246,19 +246,39 @@ Then install relevant development requirements:
 #. pip install -r requirements.txt
 #. pip install -r tests/requirements.txt
 
+Once you have finished your changes, please provide test case(s), relevant documentation
+and update CHANGELOG.rst.
 
-In order to update test environment, and documentation, additional steps are
-required:
+.. note::
+
+    As to rnd_requirements.txt, usually, it is created when a dependent
+	library is not released. Once the dependecy is installed
+	(will be released), the future
+	version of the dependency in the requirements.txt will be valid.
+
+
+How to test your contribution
+------------------------------
+
+Although `nose` and `doctest` are both used in code testing, it is adviable that unit tests are put in tests. `doctest` is incorporated only to make sure the code examples in documentation remain valid across different development releases.
+
+On Linux/Unix systems, please launch your tests like this::
+
+    $ make
+
+On Windows systems, please issue this command::
+
+    > test.bat
+
+How to update test environment and update documentation
+---------------------------------------------------------
+
+Additional steps are required:
 
 #. pip install moban
 #. git clone https://github.com/pyexcel/pyexcel-commons.git commons
 #. make your changes in `.moban.d` directory, then issue command `moban`
 
-What is rnd_requirements.txt
--------------------------------
-
-Usually, it is created when a dependent library is not released. Once the dependecy is installed(will be released), the future version of the dependency in the requirements.txt will be valid.
-
 What is pyexcel-commons
 ---------------------------------
 
@@ -269,18 +289,15 @@ What is .moban.d
 
 `.moban.d` stores the specific meta data for the library.
 
-How to test your contribution
-------------------------------
-
-Although `nose` and `doctest` are both used in code testing, it is adviable that unit tests are put in tests. `doctest` is incorporated only to make sure the code examples in documentation remain valid across different development releases.
-
-On Linux/Unix systems, please launch your tests like this::
+Acceptance criteria
+-------------------
 
-    $ make
+#. Has Test cases written
+#. Has all code lines tested
+#. Passes all Travis CI builds
+#. Has fair amount of documentation if your change is complex
+#. Agree on NEW BSD License for your contribution
 
-On Windows systems, please issue this command::
-
-    > test.bat
 
 
 License
diff --git a/django_excel.yml b/django_excel.yml
@@ -1,6 +1,7 @@
 overrides: "pyexcel.yaml"
 name: "django-excel"
-version: 0.0.6
+version: 0.0.7
+current_version: 0.0.7
 release: 0.0.6
 webframework: Django
 dependencies:
diff --git a/doc/source/conf.py b/doc/source/conf.py
@@ -23,7 +23,7 @@
 project = u'django-excel'
 copyright = u'2015-2017 Onni Software Ltd.'
 version = '0.0.6'
-release = '0.0.6'
+release = '0.0.7'
 exclude_patterns = []
 pygments_style = 'sphinx'
 import os  # noqa
diff --git a/setup.py b/setup.py
@@ -10,7 +10,7 @@
 
 NAME = 'django-excel'
 AUTHOR = 'C.W.'
-VERSION = '0.0.6'
+VERSION = '0.0.7'
 EMAIL = 'wangc_2011@hotmail.com'
 LICENSE = 'New BSD'
 DESCRIPTION = (
