-
Notifications
You must be signed in to change notification settings - Fork 69
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
Roadmap to 1.0 Release #149
Comments
<3 to see the authenticator being pushed forward. THANK YOU, @lambdaTotoro :) |
Mee too!!! Thank you @lambdaTotoro!! I'll try contribute to the review process of the PRs, feel free to ping me about anything regarding this repo's maintenance @lambdaTotoro! |
I have decided to move some of the issues above to the next milestone. This is partially motivated by wanting to use the new version out-of-the-box (i.e. from pip) for the new semester, and partially because I don't want to stall this any longer and the bulk of the work has already been done. Hence, I have just released Version 1.0.0 ! Thanks again to @consideRatio and @davidedelvento who both contributed a lot to this. I'll close this issue, but of course, work remains to be done! |
THANK YOU @lambdaTotoro AND EVERYONE INVOLVED! WIEEE :D 🎉 ❤️!! |
Thank you @lambdaTotoro |
I've been talking with @consideRatio about moving this project forward.
Here's what I think would need to happen for me to be happy to call it
1.0
, roughly in order of (estimated) difficulty.Roadmap
- [ ] Log in users directly after sign-up, if there's no need for authorisation. (Log user in automatically after sign-up #72)After all of that is done:
- [ ] We're getting a lot of issues in the context of TLJ and Docker, I'd like to have a tried-and-tested config available for that.But if anyone else (especially @leportella, @consideRatio and @yuvipanda) have more ideas or any form of input, I'll be very happy to hear it.
The text was updated successfully, but these errors were encountered: