Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

if it is an actual issue that ought to be fixed but you don't have the resources to do it, then it could be moved to a backlog instead closing it as "won't fix". the backlog is the documentation of all the issues and it is clear that there is no plan to fix something in the backlog. that way it works for both types.
 help



> the backlog is the documentation of all the issues and it is clear that there is no plan to fix something in the backlog.

I don't understand. How is this backlog different from "Closed won't fix", other than the name?


sorry, my phrasing was sloppy. i meant:

the backlog is the documentation of all open issues for which there is not yet a plan or resource to fix them.

backlog means: this should be looked at at some point. closed, for whatever reason means: this is resolved, no need to look at it any further. can be deleted/archived.

you only close as "won't fix" if you are positive that you do not even want to fix this issue even if you could, because it is not actually an issue, it works as designed, it's a feature you don't want to add, etc. issues that you can't fix right now or even in the foreseeable future, but nevertheless want to fix because they are actual issues, go into the backlog.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: