-
Notifications
You must be signed in to change notification settings - Fork 459
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 maintained? #472
Comments
Here is a good thread on this topic: #414 Short version: this module has reached a steady state that doesn't demand, currently, a lot of iteration. Most activity occurs in supporting modules. |
As a sub note: we still use Kraken internally with over 130 applications in production and growing. Over 300 millions requests per day on average. |
There will be some new examples, documentation, and modules out soon around usage of react/webpack. We also plan to reboot our krakenjs.com website soon. |
Thank you. I am happy to hear this. tl;dr Yes |
Unquestionably, a number of the kraken (org, not module) repos need a bit of spit-shine. The team has been stretched a bit thin and, speaking personally, I had to take a bit of a break from things due to some personal life changes. While I'm with @tlivings on the relatively feature-completeness of kraken (module, not org), issues and pull-requests have gotten stale—a lot of that is on me. Hopefully we can clean some of that up soon which—in addition to the updates @grawk pointed out—should help in fixing the questionable perception. |
There seems to have been a sharp drop-off in activity here and I'm wondering if I should use this or not on a new project. Is there any official word on the status of kraken development?
The text was updated successfully, but these errors were encountered: