Possible breaking changes for 1.0

[matmair]

With somewhat soon (once #5212 is done) 1.0 approaching, we can start thinking about breaking changes we might want to implement to make long-term maintainability easier.

Tasks

Beta Give feedback

1. Squash migrations for 1.0 #5015
   CI refactor setup +3
2. [FR] Restructure code #5578
   breaking documentation enhancement question refactor +5
   
3. moving config files out of the code source
4. do not require any envs on docker startup, assume local subfolder /data
5. rename default python env to .venv
6. respect AUTH_USER_MODEL Support custom user model #6418
7. Raising minimum python tp 3.10 #6420 raise to py 3.10
8. rename master to main
9. Remove django-otp migration introduced in Remove django-allauth-2fa, dj-rest-auth and django-user-sessions  #6293

See also this discussion #6173 (comment)

[matmair]

Thoughts @inventree/maintainer @inventree/triage

[matmair]

Open to more ideas if others arise

[matmair]

Another point of discussion: rename the latest branch from master to main. The latter becomes more and more the default and I think that it also is the more logical naming. Thoughts @SchrodingersGat?

[SchrodingersGat]

Another point of discussion: rename the latest branch from master to main. The latter becomes more and more the default and I think that it also is the more logical naming. Thoughts @SchrodingersGat?

Not opposed to that