Skip to content
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

Open
valberg opened this issue Nov 5, 2021 · 8 comments
Open

Plan for a 1.0 release #119

valberg opened this issue Nov 5, 2021 · 8 comments
Milestone

Comments

@valberg
Copy link
Collaborator

valberg commented Nov 5, 2021

I was thinking that we should have a plan for a 1.0 release where we define:

  • a deprecation policy
  • a policy for which versions of dependency to support
  • a versioning scheme (semver is fine, but we should be explicit about what we use)
@akx
Copy link
Member

akx commented Dec 7, 2021

Should we do one more <1.0 release (0.9?) that

  • has changes since 0.8 (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?

@clokep
Copy link
Collaborator

clokep commented Dec 7, 2021

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:

  1. Ensure the release notes were up-to-date (and double check the date on it).
  2. Update the version number in setup.py
  3. Commit
  4. Tag
  5. git clean -dxf
  6. python setup.py bdist_wheel sdist
  7. twine check dist/*
  8. 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. 🤷

@valberg
Copy link
Collaborator Author

valberg commented Dec 7, 2021

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 :)

@monosans
Copy link
Contributor

monosans commented May 1, 2023

How about an intermediate release of v0.11 now? A lot of changes have accumulated that would be nice to have.

@jkaeske
Copy link
Contributor

jkaeske commented Jun 3, 2023

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?

@federicobond
Copy link

Hi @akx, is there any way I can help push a new release of the library out?

@akx
Copy link
Member

akx commented Jul 4, 2023

@monosans @jkaeske @federicobond @matmair @SchrodingersGat

0.11.0 released (with the fancy new Trusted Publisher system too) 🎉

@matmair
Copy link

matmair commented Jul 4, 2023

You rock @akx @valberg !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants