The Datatracker draft tracking service
(for the IETF Secretariat)
So, for the same document, we're seeing four state transitions. Only the
final one is of interest to someone that's just monitoring to see if
something's new. The rest are useful to help see whether stuff might be
"stuck" for some reason.
Similarly, transitions for documents going through IESG review get very
noisy as well, but for different reasons.
I haven't gotten around to implementing body level filtering to try to pull
out these transitions, but that's eventually where I think this might take
me. Mostly I've just been leaning on my delete key a lot.
What might be somewhat more helpful is including something in the message
headers, or even subject, that provides enough information to safely do
filtering. An X-Datatracker-State-Reason or something similar perhaps.
-- Jeff
Issue migrated from trac:2316 at 2022-03-04 05:53:29 +0000
type_enhancement
| by jhaas@pfrc.orgCopying an email with Henrik: Henrik,
Are the emails that come from the data tracker something that's in the code maintained by those working on the datatracker software?
If so, has there been any discussion about how to make them less chatty?
To give an example:
Hello,
This is a notification from the Personal ID list of jhaas@pfrc.org.
Document: draft-ietf-idr-bgpls-segment-routing-epe, https://datatracker.ietf.org/doc/draft-ietf-idr-bgpls-segment-routing-epe/
Change: Uploaded new revision
Best regards,
Hello,
This is a notification from the Personal ID list of jhaas@pfrc.org.
Document: draft-ietf-idr-bgpls-segment-routing-epe, https://datatracker.ietf.org/doc/draft-ietf-idr-bgpls-segment-routing-epe/
Change: Request for posting confirmation emailed to previous authors: Stefano Previdi , idr-chairs@ietf.org, Saikat Ray , Keyur Patel , Jie Dong , Clarence Filsfils
Best regards,
Hello,
This is a notification from the Personal ID list of jhaas@pfrc.org.
Document: draft-ietf-idr-bgpls-segment-routing-epe, https://datatracker.ietf.org/doc/draft-ietf-idr-bgpls-segment-routing-epe/
Change: New version available: draft-ietf-idr-bgpls-segment-routing-epe-13.txt
Best regards,
Hello,
This is a notification from the Personal ID list of jhaas@pfrc.org.
Document: draft-ietf-idr-bgpls-segment-routing-epe, https://datatracker.ietf.org/doc/draft-ietf-idr-bgpls-segment-routing-epe/
Change: New version approved
Best regards,
So, for the same document, we're seeing four state transitions. Only the final one is of interest to someone that's just monitoring to see if something's new. The rest are useful to help see whether stuff might be "stuck" for some reason.
Similarly, transitions for documents going through IESG review get very noisy as well, but for different reasons.
I haven't gotten around to implementing body level filtering to try to pull out these transitions, but that's eventually where I think this might take me. Mostly I've just been leaning on my delete key a lot.
What might be somewhat more helpful is including something in the message headers, or even subject, that provides enough information to safely do filtering. An X-Datatracker-State-Reason or something similar perhaps.
-- Jeff
Issue migrated from trac:2316 at 2022-03-04 05:53:29 +0000