doc(platforms): inform more clearly about best-effort

This has been the case for Windows as well, and is now
made official.
Certain tests already fail on windows, for example.

Author: Byron

README.md

@@ -54,6 +54,11 @@ codebase for `__del__` implementations and call these yourself when you see fit.
 Another way assure proper cleanup of resources is to factor out GitPython into a
 separate process which can be dropped periodically.
 
+#### Best-effort for Python 2.6 and Windows support
+
+This means that support for these platforms is likely to worsen over time
+as they are kept alive solely by their users, or not.
+
 ### RUNNING TESTS
 
 *Important*: Right after cloning this repository, please be sure to have executed the `init-tests-after-clone.sh` script in the repository root. Otherwise you will encounter test failures.

doc/source/index.rst

@@ -9,7 +9,6 @@ GitPython Documentation
    :maxdepth: 2
 
    intro
-   whatsnew
    tutorial
    reference
    roadmap

doc/source/intro.rst

@@ -15,7 +15,7 @@ Requirements
 
 * `Python`_ 2.7 or newer
     Since GitPython 2.0.0. Please note that python 2.6 is still reasonably well supported, but might
-    deteriorate over time.
+    deteriorate over time. Support is provided on a best-effort basis only.
 * `Git`_ 1.7.0 or newer
     It should also work with older versions, but it may be that some operations
     involving remotes will not work as expected.
@@ -75,6 +75,12 @@ codebase for `__del__` implementations and call these yourself when you see fit.
 Another way assure proper cleanup of resources is to factor out GitPython into a
 separate process which can be dropped periodically.
 
+Best-effort for Python 2.6 and Windows support
+----------------------------------------------
+
+This means that support for these platforms is likely to worsen over time
+as they are kept alive solely by their users, or not.
+
 Getting Started
 ===============