-
Notifications
You must be signed in to change notification settings - Fork 27.8k
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
Too many open issues to be taken seriously by enterprise #3212
Comments
I also think we have many issues open but if you check they are more about doubts or feature requests than bugs. |
Wow that was quick! Yep indeed, everything is fine and I'm not blaming anyone. But imo it's kinda bad press to see this many open issues. This was the first thing popped in my mind when scanning the repo. Some of these are more than a year old. https://github.com/zeit/next.js/issues?page=10&q=is%3Aissue+is%3Aopen Indrek |
Fair point. 👍 |
I think this NextJS is too cool and advanced for Enterprise |
@wesharehoodies Consider how active these issues and PRs are though.. (make sure you're "watch"ing the repo) Also, many of the issues are feature requests, and many are "help me with this please", which are much more positive that bug reports. |
It's not that simple. All open PRs are either things we still have to look into or things we have to work on to improve / expand 😄
Like @sergiodxa mentioned most projects have at least 3 times more issues at this scale (almost 19K stars). Also note that github issues are an endless lifecycle which can't be tamed. There will always be issues popping up 😄. Most are feature requests like @mattbrunetti said. I do agree that we should do a run through all issues to see if they're still relevant.
To expand on this. On the contrary to what you're saying we're seeing great adoption across many different types of companies, from startups to large enterprises. People are even creating ecommerce experiences using Next 💯 Some examples: npm - https://www.npmjs.com/search?q=next A while ago, before the v2 release, I made a list in this issue: #1458 |
In light of closing issues, feel free to close this one if your question is answered 😄 🙌 |
Anyone else enjoying the irony of this issue? 🤣 |
Alright, fair ball play. Love you guys ❤️ |
Just joining to the conversion. I think measuring the project by the number of open issues is hard (when deciding good or bad). In our case, we have a higher number of open issues because of the following reasons.
Next.js is very crucial for us since we use it for our web app and for our Desktop client. So, we are seriously serious about Next.js for sure :) |
@wesharehoodies ❤️ |
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread. |
Hello, big fan of Next.
But-- there are too many issues open for any big company to adapt to Next.
Can we close some of the issues? Also, can we close some of the PR's as well--limiting to around 15 open PR's max?
Yours truly,
Indrek
The text was updated successfully, but these errors were encountered: