summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorSebastian Thiel <byronimo@gmail.com>2015-01-04 19:14:33 +0100
committerSebastian Thiel <byronimo@gmail.com>2015-01-04 19:14:33 +0100
commitf6aa8d116eb33293c0a9d6d600eb7c32832758b9 (patch)
treeee07288965cfd4e8326c57735e94c347ee7dd829 /README.md
parent3936084cdd336ce7db7d693950e345eeceab93a5 (diff)
downloadgitpython-f6aa8d116eb33293c0a9d6d600eb7c32832758b9.tar.gz
initial set of adjustments to make (most) imports work.
More to come, especially when it's about strings
Diffstat (limited to 'README.md')
-rw-r--r--README.md4
1 files changed, 0 insertions, 4 deletions
diff --git a/README.md b/README.md
index 4b678184..1bc6430e 100644
--- a/README.md
+++ b/README.md
@@ -83,10 +83,6 @@ In short, I want to make a new release of 0.3 with all contributions and fixes i
The goals I have set for myself, in order, are as follows, all on branch 0.3.
-* bring the test suite back online to work with the most commonly used git version
-* merge all open pull requests, may there be a test-case or not, back. If something breaks, fix it if possible or let the contributor know
-* conform git-python's structure and toolchain to the one used in my [other OSS projects](https://github.com/Byron/bcore)
-* evaluate all open issues and close them if possible
* evaluate python 3.3 compatibility and establish it if possible
While that is happening, I will try hard to foster community around the project. This means being more responsive on the mailing list and in issues, as well as setting up clear guide lines about the [contribution](http://rfc.zeromq.org/spec:22) and maintenance workflow.