Should we push another version?

[tburrows13]

Is it time to push another version (0.2.2.14?) to PyPI? Are the certain things we are waiting for before we have another release?

[keikoro]

I think merging the most recent "trivial" PRs that are still open would be a good idea before releasing a new version.

[ghost]

I think it would be good to add some additional tests too. Currently our code coverage is 47% (which is up from 22% the beginning of the month)..

[ghost]

I'm thinking we should push another version out to PyPI. Anyone know (or has access) to do with with moviepy? We have 13 remaining PR's, and we have 50% code coverage at this point.

[tburrows13]

Yes please! We have issues solved a month (or so) ago that haven't been fixed in the PyPI version yet. @Zulko...?
The last update was on the 15th of Feb...!

[mbeacom]

@Earney I'm not sure who all was added to pypi, but I can push updates whenever is agreed.

[tburrows13]

I'd say ASAP

[ghost]

I agree. as soon as possible. The last release was done Feb 15th, (almost 2 months ago).

…

On Tue, Apr 4, 2017 at 3:29 PM, Gloin1313 ***@***.***> wrote: I'd say ASAP — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#481 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABGu8uX-XPsu80Ghip_X26MKLaDhtxXrks5rsqhHgaJpZM4MaWCT> .

[mbeacom]

Please see: Release v0.2.3.1
Wheel and source pushed to pypi.

[tburrows13]

Great! Thanks