I know this is a bit cliche-ish, but documentation is always a great place
to start.
1) Fresh perspective is always valuable. As developers get
"self-indoctrinated", we get used to various gaps in the documentation such
that they become blind spots for us. This is why the sign of a healthy
project
I have tagged 1.4.0, posted the source tarball to sf, updated pypi,
updated the docs, and kicked off building the mac wheels.
Holding off on announcing to the rest of the lists until the windows
binaries get built.
Created a v1.4.0-doc branch on the main repo to put documentation
updates in. One
On 8/25/2014 8:25 PM, Thomas Caswell wrote:
> I have tagged 1.4.0, posted the source tarball to sf, updated pypi,
> updated the docs, and kicked off building the mac wheels.
>
> Holding off on announcing to the rest of the lists until the windows
> binaries get built.
>
> Created a v1.4.0-doc branc
