Prepare for release v2.4.12

[althonos]

Type of changes

• Other

Description

Here it is, release v2.4.12, a little more than one year after the previous one! The goal was to get some bug fixes before Python 2.7 reaches EOL.

About the project organisation:

• I moved PULL_REQUEST_TEMPLATE.md to .github and removed the check boxes from the categories, since GitHub would mistake them for a checklist.
• I added a copyright line about contributors in LICENSE.
• I replaced the @willmcgugan mention by @Pyfilesystem/maintainers in the pull request template.
• I added myself as a maintainer to the PyPI metadata
• I moved all project metadata to setup.cfg instead of previously having half in setup.py and half in setup.cfg

Then we probably need to setup Travis-CI to deploy to PyPI, and we should be in the clear.

ping @PyFilesystem/maintainers

[chfw]

Could I recommend the project to use this git branching model?

In short: features branches ---merge---> develop branch ---release---> master

Benefit: it is quick to see what's been changed in code when it is compared with the master(the previous version).

Of course, with github, it is still possible to do version comparison between tags. But it is, in my humble opinion, better work flow.

[althonos]

Hi @willmcgugan ,

we have had some important bugfixes recently, and it would be amazing if we could release before we start introducing some breaking changes like #431.

Would you be able to make me a co-maintainer on PyPI? I can setup Travis to deploy releases to PyPI but for now you are still the only one able to make releases there. Cheers!

[willmcgugan]

Hi @althonos

That's fantastic. Yes, happy to add you as co-maintainer. I guess I'll need your PyPi handle?

[althonos]

@willmcgugan : Great! It's the same as here, I'm althonos 😉

[willmcgugan]

Of course! Invite sent...