The branch 1.4.x was the branch for bug fixes that would eventually turn
into the _next_ 1.4 series release. We do not plan on doing a 1.4.4 so the
1.4.x branch no longer is needed. The commit used for the releases are
tagged (ex v1.4.3). The v1.4.3-doc branch is so that we can correct any
docum
I am in favor of doing in in PR comments so we can to line comments.
On Sun, Apr 26, 2015 at 3:47 AM Nicolas P. Rougier
wrote:
>
> Great ! Thanks for setting this up. One comment, it would be great to have
> a README.rst in the directory to have abstract of all MEPS at once in
> github (I can ma
So it seems I was using the old branch (now deleted?) v1.4.x rather than
v1.4.3-doc, which does have the commit for the fix in question. I was
naively assuming that v1.4.x was always the latest release in the v1.4
series.
False alarm. Sorry.
M
On 4/25/15 4:26 PM, Thomas Caswell wrote:
> The c
Great ! Thanks for setting this up. One comment, it would be great to have a
README.rst in the directory to have abstract of all MEPS at once in github (I
can make a PR).
I've started working on MEP28
(https://github.com/rougier/matplotlib/blob/MEP28/doc/devel/MEP/MEP28.rst). I
intend to mak
