Thanks. I guess we should never set the trunk status as `disabled` when we pref off a feature on trunk for all channels, or else the bot thinks the bug still affects all future versions. I filed https://github.com/mozilla/bugbot/issues/2403 on seeing if we can make the bot handle this more gracefully/helpfully.
Bug 1894614 Comment 20 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks. I guess the upshot of the bot issue is that we should never set the trunk status as `disabled`, when we fix a bug by preffing off a feature on trunk (not in a version-specific way channels). Otherwise the bot implicitly thinks the bug still affects all future versions. I filed https://github.com/mozilla/bugbot/issues/2403 on seeing if we can make the bot handle this more gracefully/helpfully.
Thanks. I guess the upshot of the bot issue is that we should never set the trunk status as `disabled`, when we fix a bug by preffing off a feature on trunk indefinitely (i.e. not in a way where version numbers are relevant). Otherwise, the change from affected-to-disabled makes the bot implicitly think the bug will still affect future versions. I filed https://github.com/mozilla/bugbot/issues/2403 on seeing if we can make the bot handle this more gracefully/helpfully.