Martin Sebor wrote:
The issue should be linked as a duplicate of STDCXX-614 and on closing the Status set to Duplicate. We might also need to edit the time tracking info so we don't throw off our reporting (I don't know if it would).
Keep in mind, although time tracking is interesting data (even as an open source effort), while you have a community project we need to recognize it's only a rough approximation. Using this as any sort of bookkeeping feature for corporate analysis would be abusing the process. So I agree(d) with turning on the feature, understanding what parts of the code demand the most attention (or possibly also the most audit-from-behind based on the amount of effort expended in certain areas of the code). But I'd disagree if this was expected to be 100% spot-on with the specific time used, and would caution that this feature is essentially opt-in/voluntary and probably variable when it comes to multi-day review of a bug.
