There are a few bugs around bug heat. This particular one appears to be negatively impacting package copying, and from my reading of the code bug filing and retargeting etc also triggers a cache update on the context.
In the short term, I think we need to keep the current implementation of the heat cache, though we did discuss some improvements that would be more efficient @ the epic. However, are there any issues with just-in-time updates of the cache and depending on the backend updates (which I believe is job based) instead? Alternatively, we could move to an incremental algorithm: add the delta of the bugs heat to the target's total, change the max IF the bug has the contexts peak heat already. Your thoughts solicited :) -Rob _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
