Something I thinked about recently.

Something I thinked about recently. Currently bug tracker have plenty of "Resolved" issues from prior releases that isn't closed which make bug tracker a bit harder to use. There is clearly reason to keep recently fixed issues visible, but that isn't the case for anything that several years old.

My idea is let's set some rule on resolved issue closing. For example to close all issues that was resolved before prior stable release: current stable release we have is 0.98 so we'll close all issues that marked as resolved for stable 0.97 and older.

So once 0.99 released we'll close all issues resolved for 0.97b, 0.97c and 0.98.

結果 (中文) 1:

我认为对的东西最近。目前 bug 追踪器，有的是不封闭的先前版本，让一个 bug 跟踪系统和有点难使用从"已解决"的问题。显然是理由保持最近固定的问题可见，但事实并非如此的东西，是几岁。我的想法是，让我们设置一些规则，他解决了问题关闭。为例，关闭所有问题解决后，再以前的稳定版本: 当前的稳定版本，我们已经为 0.98，所以我们会都关闭所有标记为已解决稳定 0.97 和老年人的问题。所以一旦 0.99 释放我们会关闭为 0.97 (b) (c) 0.97 和 0.98 解决的所有问题。

結果 (中文) 3:

关于什么的，thinked recently。目前有很多bug跟踪从之前的“resolved releases”问题，不是封闭的，这是讲的努力让bug跟踪一位使用。有明确的原因让recently visible固定问题，但这不是什么情况，为几岁。我们的想法是让他resolved关闭一些规则集的问题。例如，你所有的问题是不稳定resolved之前释放电流稳定释放之前：我们拥有的是0.98会关闭所有标记为resolved问题，为稳定0.97和老年。所以一旦被释放，我们将关闭所有0.99 resolved为0.97b问题，0.97c和0.98。