-
Notifications
You must be signed in to change notification settings - Fork 101
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
is this project still activelly developed? #511
Comments
This package is great and I too would like to know about its future. Thanks for all of your efforts! |
btw, I just found this issue which spells out the future. |
I switched jobs to a job that does not use SQL Server not too long after taking the lead on the last major upgrade, which means I don't have the capacity/motivation to actively maintain the repo. I can tend to pull requests to the best of my ability (i'm not sure if there's any other active contributors with the ability to do so), but I have definitely not been able to organize bug fixes and new updates, etc. I believe I also don't have the ability to name admins/maintainers in the github organization, but if someone is willing to take up the torch I can try to see what we need to do to pass it on. for now, tagging me on here is probably the best way to get my attention if active help is needed (I have a little more time for side quests now that i've settled into the new job a bit, but not too much) but I'm not aware of any active developments or maintenance work happening, to try to answer the original question. Whether or not you are able to "rely" on it is up to you but I would not expect quick turn around for new features or bug fixes, especially when considering the state of dbt's extension/testing ecosystem, maybe that's gotten better in the last year but when we were in there it was a headache. |
@cody-scott congratulations, you are now an admin 🙂 |
It would be great to have some indication of whether this project can be relied upon in the foreseeable future, specifically whether bugs will be actively resolved and development will continue.
The text was updated successfully, but these errors were encountered: