A "bug" is normally seen as an impediment to some execution, generally by creating a unworkable situation. Outside of that, a different way of successfully executing can only be labelled a bug when it does not conform to a given specification. If it becomes acceptable, then the specification changed and therefore the bug does not exist anymore.
Your question seems to imply that bugs fixes don't get prioritized. I believe that prioritizing should happen somewhat frequently, and that features and bugs should both be treated equally as "issues". Bugs will often be higher-priority than a new feature, but that shouldn't be an automatic decision.
I believe that the bug is still a bug no matter when it is discovered in the project lifecycle, and should be defined and documented as such. Remember, documenting a bug does not make it a feature :D
Are your developers giving you the "That ain't a bug, it's a feature!" line?
Seriously, a "bug" would be something in the applications that behaved counter to the specifications of the project. Unless the specifications change, I would not expect a bug to ever expire.
发布评论
评论（5）
“错误”通常被视为某些执行的障碍，通常是通过创建不可行的情况来实现的。除此之外，成功执行的不同方式只有在不符合给定规范时才能被标记为错误。如果它变得可以接受，那么规范就会发生变化，因此该错误将不再存在。
A "bug" is normally seen as an impediment to some execution, generally by creating a unworkable situation. Outside of that, a different way of successfully executing can only be labelled a bug when it does not conform to a given specification. If it becomes acceptable, then the specification changed and therefore the bug does not exist anymore.
您的问题似乎暗示错误修复没有得到优先考虑。我认为优先级划分应该经常发生，并且功能和错误都应该被平等地视为“问题”。错误通常比新功能具有更高的优先级，但这不应该是一个自动决定。
Your question seems to imply that bugs fixes don't get prioritized. I believe that prioritizing should happen somewhat frequently, and that features and bugs should both be treated equally as "issues". Bugs will often be higher-priority than a new feature, but that shouldn't be an automatic decision.
我相信，无论在项目生命周期中何时发现该错误，该错误仍然是一个错误，并且应该如此定义和记录。请记住，记录错误并不意味着它成为一个功能 :D
I believe that the bug is still a bug no matter when it is discovered in the project lifecycle, and should be defined and documented as such. Remember, documenting a bug does not make it a feature :D
您的开发人员是否向您传达“这不是错误，而是功能！”的信息？线？
认真地说，“错误”是应用程序中与项目规范相反的行为。除非规范发生变化，否则我不认为错误会过期。
Are your developers giving you the "That ain't a bug, it's a feature!" line?
Seriously, a "bug" would be something in the applications that behaved counter to the specifications of the project. Unless the specifications change, I would not expect a bug to ever expire.
当您更改规格以响应它时。
When you change the specification in response to it.