-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plan for a 1.0 release #119
Comments
Should we do one more <1.0 release (0.9?) that
and then drop testing for EOL versions of Django for the forthcoming 1.0? |
Please shout if you need help doing the release! I think I dropped what I used to do into an email, but to put it in public:
Some of the ecosystem has moved on since then, but I think the above should still work OK. 👍 Other things to check are that access to ReadTheDocs works properly. It might make sense to do a 0.9 just to ensure all the processes work OK. 🤷 |
Yeah I think that is a very good idea! My thoughts were more in the planning department, ie. what do we want to have before we can release a version 1.0 :) |
How about an intermediate release of v0.11 now? A lot of changes have accumulated that would be nice to have. |
Any news on this release? |
Hi @akx, is there any way I can help push a new release of the library out? |
@monosans @jkaeske @federicobond @matmair @SchrodingersGat 0.11.0 released (with the fancy new Trusted Publisher system too) 🎉 |
I was thinking that we should have a plan for a 1.0 release where we define:
The text was updated successfully, but these errors were encountered: