Roundup Tracker - Issues

Message3715

Author richard
Recipients richard, stefan
Date 2009-06-01.00:40:03
Message-id <84543419-FFE7-42F3-80D9-64EE6045E371@mechanicalcat.net>
In-reply-to <4A231C9B.3030809@codesourcery.com>
On 01/06/2009, at 10:11 AM, Stefan Seefeld wrote:
> Richard Jones wrote:
>>> Is there any reason this code could not be moved into the  
>>> nosyreaction
>>> class itself (or a baseclass, if it is used elsewhere, too) ? That
>>> would
>>> allow it to be customized.
>>
>> It was moved into the roundup core to facilitate bug fixing without
>> requiring users to reinstall their detectors every release.
>
> I don't quite understand what you are saying. Why would users have to
> reinstall anything for 'every release', if this was in a detector ?

Back in the bad old days this actually was an issue. There would be a  
bug fixed in the nosy reactor code, and everyone would have to update  
their trackers' copies of the detectors to fix the bug, rather than  
just upgrade the roundup lib install. "every release" was an  
unfortunate overstatement. Obviously they'd only have to update their  
detectors if there was a bug fixed in there (though that means of  
course that they have to keep a close eye on the CHANGES / upgrading  
file and we'd have to make sure we document the need to update  
detectors...)
History
Date User Action Args
2009-06-01 00:40:03richardsetrecipients: + richard, stefan
2009-06-01 00:40:03richardlinkissue2550551 messages
2009-06-01 00:40:03richardcreate