You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A junk report creates an entry both when the report generated and when it's deleted. For example, see https://datatracker.ietf.org/doc/rfc1/history/. This creates noisy histories for an RFC.
Perhaps errata state changes should not be captured on the History tab at all, or perhaps there should be lag between the time it's reported and when it's added to the History page so that there's time for a junk report to be deleted.
Description
A junk report creates an entry both when the report generated and when it's deleted. For example, see https://datatracker.ietf.org/doc/rfc1/history/. This creates noisy histories for an RFC.
Perhaps errata state changes should not be captured on the History tab at all, or perhaps there should be lag between the time it's reported and when it's added to the History page so that there's time for a junk report to be deleted.
Code of Conduct
The text was updated successfully, but these errors were encountered: