Polaris Cleanup: Triage existing issues

[MelSumner]

After shipping Polaris, we need to clean up issues:

Evaluate existing issues:

• try to reproduce the issue
• if there's a reproduction, try to do it on the most recent LTS of Ember

Guidance per project:

• Ember Data: if the issue is open, it should be open (regularly triaged)
• Ember CLI: if it's older than 2 years, close the issue
• Ember JS: try to reproduce;
• • if it's an old issue and it doesn't make sense, especially post-Polaris, it's okay to close
• • if it seems to still be an issue, then give it a "still an issue" label
• • if it's a feature we no longer support (e.g. pods) then close the issue with "won't fix"

Phrasing to use when closing issues:

"Unable to reproduce this issue; due to its age, closing issue. Please re-open with reproduction if you feel as though this is still an issue for you."

"This feature is no longer recommended or supported in Ember. Closing issue."

[sandstrom]

Great initiative @MelSumner!

I worked through and closed ~30 issues a few weeks ago.

Here is another suggestion on wording (your's are good too!):

Non-issues (questions etc)

I'm doing some issue gardening 🌱🌿 🌷 and came upon this issue. 

This seem like more of a question than a bug report/issue, and therefore better suited for the forums: https://discuss.emberjs.com/

Also, the reality for any open-source framework, relying on individuals to put in the work, is that there isn't always time to answer all questions.

If you want to pay back to the community, one easy thing is to ask one question in the forum (your current one), and also try to answer 2 questions from other people.

If you think this is an error, a reproduction of the bug and a more extensive explanation would be a good start. Then, if others agree it's a bug, the second step is often to dig in and write a patch to fix the bug.

I'll be closing this for now though, to keep the list of open issues manageable. I hope you understand.

Asking if it's still relevant

I'm doing some issue gardening 🌱🌿 🌷 and came upon this issue. Since it's quite old I just wanted to ask if this is still relevant? If it isn't, maybe we can close this issue?

By closing some old issues we reduce the list of open issues to a more manageable set.
This issue has been open for a while without anyone jumping in to fix it. The reality is that unless you want to fix the bug itself, it will likely stay that way.

Closing

I'm doing some issue gardening 🌱🌿 🌷 and came upon this issue.

This repo has a lot of open issues, some that that have been open for several years. The reality is that this is an open-source project, and the time of core team members is very limited.

I'll be closing this for now though, to keep the list of open issues manageable. I hope you understand. We all want them to focus on moving the framework forward (high-leverage things).

I'll be closing this for now though, to keep the list of open issues manageable. I hope you understand.

If you disagree, we can reopen, but in that case, you help in fixing this would be appreciated (for example a PR with a bugfix).