Skip to content

Commit e41c727

Browse files
committed
README: Added mailing list and issue tracker information
Docs: updated roadmap
1 parent 143b927 commit e41c727

File tree

3 files changed

+22
-14
lines changed

3 files changed

+22
-14
lines changed

README

+8
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,14 @@ git clone git://gitorious.org/git-python/mainline.git git-python
4343
git clone git://github.com/Byron/GitPython.git git-python
4444

4545

46+
MAILING LIST
47+
============
48+
http://groups.google.com/group/git-python
49+
50+
ISSUE TRACKER
51+
=============
52+
http://byronimo.lighthouseapp.com/projects/51787-gitpython/milestones
53+
4654
LICENSE
4755
=======
4856

doc/intro.rst

+8-1
Original file line numberDiff line numberDiff line change
@@ -78,9 +78,16 @@ and cloned using::
7878
$ git clone git://gitorious.org/git-python/mainline.git git-python
7979
$ git clone git://github.com/Byron/GitPython.git git-python
8080

81+
Mailing List
82+
============
83+
http://groups.google.com/group/git-python
84+
85+
Issue Tracker
86+
=============
87+
http://byronimo.lighthouseapp.com/projects/51787-gitpython/milestones
88+
8189
License Information
8290
===================
83-
8491
GitPython is licensed under the New BSD License. See the LICENSE file for
8592
more information.
8693

doc/roadmap.rst

+6-13
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,6 @@
1-
=====================
2-
What's next in: 0.2.0
3-
=====================
4-
1. **Docs Review**
5-
* all documentation strings must be reviewed for resT correctness. Additionally they should be adjusted to use the sphinx fields like ":param:" and ":return:".
6-
2. **Review git-python's ability to parse the progress information sent when fetching and pushing**
7-
* Up to git 1.6.5, a push would still send progress. Then up to git 1.7.0 it will not produce progress to non-ttys anymore, making git-pythons test fail. Now git is implementing new --progress flags which would allow to enforce the sending of progress messages. This needs to be researched, implementation needs adjustments to assure we get the best possible progress results with git 1.6x as well as with git 1.7x.
8-
9-
=====================
10-
What's next in: 0.2.1
11-
=====================
12-
1. **Research possibility to read the object database ( including packs and alternates support ) directly.**
13-
* Sample code can be found in dulwich, but it will have to be adjusted to perform better through configurable caching. Currently git-python can retrieve the data of about 10k smallish objects / s, the python implementation shouldn't be much slower than that.
1+
2+
#######
3+
Roadmap
4+
#######
5+
The full list of milestones including associated tasks can be found on lighthouse: http://byronimo.lighthouseapp.com/projects/51787-gitpython/milestones
6+

0 commit comments

Comments
 (0)