Release Version 0.3 about yellowbrick

[rebeccabilbro]

Closing this as @bbengfort completed this card yesterday. Time to scope out the next milestone?

[bbengfort]

@rebeccabilbro There may be a minor issue - still need to test to make sure the push to PyPI worked and that we can pip install it with ease. Saw some stuff that raised some red flags for me.

[bbengfort]

Oh, also we have to write the release notes:

https://github.com/DistrictDataLabs/yellowbrick/releases

Didn't quite get there yesterday; sorry.

[rebeccabilbro]

@bbengfort gotcha.

Issue complete when:

• pip installation issues are resolved
• release notes are written up

Let me know when you want to tag up to work on the release notes and plan the next milestone

[bbengfort]

@rebeccabilbro today and tomorrow are tough - I can do early morning Wednesday if you'd like or Thursday or Friday.

[rebeccabilbro]

@bbengfort sounds good

[bbengfort]

@rebeccabilbro - ok some folks were having trouble with this, so I just fixed the pip issue during my lunch break. However, I'm going to leave the release notes for when we can catch up; just so we're on the same page and can start the conversation.

Note, that I injected a hotfix release: 0.3.1a2 as a result of this fix. Yellowbrick should be pip installable now.

[rebeccabilbro]

Can confirm that

pip install yellowbrick

works now!

[bbengfort]

For python 2 and 3!

Ben

On Tue, Oct 11, 2016 at 2:23 PM, Rebecca Bilbro [email protected]
wrote:

Can confirm that

pip install yellowbrick

works now!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#41 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAth7hpqeTBn9F61eZs_TXGak-XXNMqeks5qy9QXgaJpZM4J13pW
.