Issues based on old MoviePy versions

[keikoro]

The repo currently has a large no. of open issues, the majority of which are based on old versions of MoviePy. For some we even know which exact version they are based on because we started prompting users to include the version no. (as well as Python version, OS,...) in our issue templates at some point.

It's an unrealistic expectation for us to be go through all issues and figure out if the bugs reported are still present in v2, but some have already been open for years and might realistically not be relevant anymore. Ideally, we'd batch-close everything that's likely of little relevancy today – can we differentiate between issues which feel safer to close and ones which need closer inspection based on topics/labels?

E.g. feature-request Request for a new feature or additional functionality. , performance Speed/performance of code or individual functionality. , certain environment Using moviepy with, or issues possibly stemming from specific OS/platforms/environments. tickets may well still be applicable but bug Issues that report (apparent) bugs. reports or examples Related to the code examples included in the documentation (examples dir). for older versions may not.

[keikoro]

Example: there are 126 open issues which include the words "MoviePy Version: 1.0.3" and are labelled bug Issues that report (apparent) bugs. (among other labels).

We could close the ones which contain only the bug label with a comment making people aware of the new release and to let them know we don't have the capacity to support old versions of MoviePy but would appreciate a new issue if the problem persists (or could, alternatively, offer to reopen the old issue).

[OsaAjani]

Hi @keikoro, I'm going through them piece by piece, for now I've focused on PR which is a bit longer to process because I try not to through away good ideas and code if the bug the pr fix is still present.
I expect to go a lot quicker on the issues and mostly intend to close anything published before 2.0.

[keikoro]

Hey @OsaAjani, wow, that sounds like a lot of work! But you probably know the current state of the code best (: and can therefore more easily judge what's worth keeping or what needs further investigation and which tickets are simply outdated. Thanks for doing this as well!

[OsaAjani]

PR are basically done, just waiting on a few response. I've massively closed old issues and encouraged original authors to reopen them if they think the issue is still relevant.