Replies: 4 comments 1 reply
-
I've just pushed https://github.com/nickw444/flask-ldap3-login/releases/tag/1.0.0a1 |
Beta Was this translation helpful? Give feedback.
-
Could you explain why moving branches around would result in loss of functionality? It's been almost two years since 1.0 was started. What would it take to release it? I'm happy to jump in and contribute, if needed. |
Beta Was this translation helpful? Give feedback.
-
Hi Nick, By the way, I see you've been trying to fix the tox flow issue and I wanted to say thank you for finding the time. I had a look at one fail and thought I'd found something but the LDAP3 search just isn't returning data and I'm not experienced enough to dig into why that might be. |
Beta Was this translation helpful? Give feedback.
-
Thanks Nick. I've integrated today's release and it's looking fine so far. |
Beta Was this translation helpful? Give feedback.
-
Hey @gmacon and @HeMan,
Just starting this thread to discuss roadmap toward 1.0 release, or some incremental release at this point. As we've realized, patching the recent bug in #97 wasn't able to be quickly released due to the current in-flight (and potentially untested/breaking changes on master).
In the interim I pushed a new branch (
release-0.9
) who's HEAD is the latest 0.9 release and have cherry-picked the bug fix onto it.I'm opening this discussion topic to decide how we move forward, and whether we should implement any changes to our branches in this repo.
I'm considering:
master
todevelop
.master
tomain
to align with recent Github changesHEAD
ofmain
to the latest0.9
release.This however means we lose a lot of the new
1.0
goodness we've got lately, namely linting, formatting and new CI pipeline. But perhaps that's more fuel toward the 1.0 fire?Beta Was this translation helpful? Give feedback.
All reactions