Merge lp:~intellectronica/launchpad/use-max-heat into lp:launchpad/db-devel
| Status: | Merged |
|---|---|
| Merged at revision: | not available |
| Proposed branch: | lp:~intellectronica/launchpad/use-max-heat |
| Merge into: | lp:launchpad/db-devel |
| Prerequisite: | lp:~deryck/launchpad/max-heat-by-target-511382 |
| Diff against target: |
173 lines (+28/-40) 4 files modified
lib/lp/bugs/browser/bug.py (+0/-22) lib/lp/bugs/browser/bugtask.py (+20/-4) lib/lp/bugs/browser/configure.zcml (+0/-5) lib/lp/bugs/browser/tests/bug-heat-view.txt (+8/-9) |
| To merge this branch: | bzr merge lp:~intellectronica/launchpad/use-max-heat |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Leonard Richardson (community) | Approve on 2010-02-24 | ||
| Canonical Launchpad Engineering | code | 2010-02-24 | Pending |
|
Review via email:
|
|||
| Eleanor Berger (intellectronica) wrote : | # |
| Leonard Richardson (leonardr) wrote : | # |
<leonardr> intellectronica: it seems like having a MAX_HEAT in bugtask.py would still be useful. you still use it in two different files
<intellectronica> leonardr: i use it in a test. i use the value as a default, but it will be gone with a following branch which will make sure we have max_heat populated
<leonardr> intellectronica: oh, one other question. why can't the bugheatview be a view on the bugtask?
<leonardr> (assuming views are desirable in general)
<intellectronica> leonardr: it's just a case of yagni. it wasn't such a brilliant idea to use a view to begin with.
<intellectronica> all we ever did with the view is initialize manually and call it

This branch changes the way bug heat is rendered. Instead of using a constant maximum heat, we use the max_heat value for the relevant bug target. As a result of this change, using a bug view doesn't make sense any more, since we now have to know about the target (which is only available from the bugtask).