The road to v1.0.0

[thomasf]

I've been using django-minio-storage with almost every website project I have started professionally during the last couple of years always for local development, for almost every staging environment and for a good portion of production deployments as well. I think it's time to start thinking about graduating to v1.0.0 (API stable)

There is no real hurry to get there but I see these major steps below. Since I do not expect to take some pauses from development to just be a user of minio-storage a few times It might take a year, who knows but I don't think that python 2 support is viable so it's being dropped right now so that it has no chance of influencing the design.

v0.3.x - fixed a bunch of stuff

The next release, a new feature + bug fix release that should not stir up any normal current usage. If you just have minio_storage installed in settings.py and don't use it in any intricate ways it will just keep on working.

After v0.3.0 is released I expect to keep on working on v0.3.x releases, maybe with minor breaking changes.

I am keeping some kind of a working document here https://github.com/py-pa/django-minio-storage/edit/master/CHANGELOG.md

v0.8 everything is stable + time for documentation

Minor improvements.

Given that some types of questions are coming up again and again in issues I hope to create a few tests that also serves as examples how to do some things that are commonly asked for.

Here is a draft for how such a test could work:

https://github.com/py-pa/django-minio-storage/blob/c43cb45773595761b7d5d1853aa1bc251140936d/tests/test_app/tests/custom_storage_class_tests.py

v1.0.0

This version is basically v0.6 with all compatibility for pre v0.5 features dropped.

After this point I expect to only increment the major version again If Django file storage API has an API breaking release. We will deprecate support for older Python and Django releases, when Django drops support we will drop support as well.

DISCUSS!

Just write a comment if you have anything to say about all of this.

[thomasf]

The minio-py v7 with an backwards incompatible API threw this planning off course for a while