Open valberg opened 2 years ago
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:
Unfortunately I don't think we have a releasing doc, but the steps I would follow were something like:
- Ensure the release notes were up-to-date (and double check the date on it).
- Update the version number in setup.py
- Commit
- Tag
- git clean -dxf
- python setup.py bdist_wheel sdist
- twine check dist/*
- twine upload dist/*
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. 🤷
Should we do one more <1.0 release (0.9?) that
* has changes since 0.8 ([0.8...main](https://github.com/valohai/django-allauth-2fa/compare/0.8...main)) * supports the versions of Django we currently test on
and then drop testing for EOL versions of Django for the forthcoming 1.0?
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.
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) 🎉
You rock @akx @valberg !
I was thinking that we should have a plan for a 1.0 release where we define: