Bug heat should decay over time
Bug #505849 reported by
Graham Binns
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Eleanor Berger |
Bug Description
Once the fix for bug 503745 lands, bug heat will be calculated based on the attributes of each bug. However, bug heat will only ever grow over time. To mitigate this, bug heat should decay over time, rather like karma does.
Related branches
lp:~intellectronica/launchpad/heat-decay-complete
Merged
into
lp:launchpad
- Edwin Grubbs (community): Approve (code)
-
Diff: 130 lines (+58/-2)3 files modifiedlib/lp/bugs/doc/bug-heat.txt (+8/-0)
lib/lp/bugs/scripts/bugheat.py (+18/-0)
lib/lp/bugs/scripts/tests/test_bugheat.py (+32/-2)
Changed in malone: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in malone: | |
assignee: | nobody → Tom Berger (intellectronica) |
Changed in malone: | |
status: | Triaged → In Progress |
Changed in malone: | |
milestone: | none → 10.02 |
Changed in malone: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Bugs that have ever been marked security critical stick at the top of the list for a long time. For example https:/ /bugs.edge. launchpad. net/bzr/ +bug/453104 is a completely boring bug, and decided to be so ~3 weeks ago, but it's still marked as the hottest because it was once critical.
Perhaps the decay thing will change this.
But to me this raises a question about the whole concept of decaying: if something is accidentally qualified as hot and that mistake is fixed, the heat should immediately reflect it.