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
But this is not clear in the document history, which shows the following and makes it appear that there was no following assignment:
2024-10-17 31 Jean Mahoney Request closed, assignment withdrawn: Vijay Gurbani Last Call GENART review
2024-10-17 31 Jean Mahoney Closed request for Last Call review by GENART with state 'Overtaken by Events': LC extended and new assignment made
2024-10-17 31 Jean Mahoney Request for Last Call review by GENART is assigned to Vijay Gurbani
We will look at improving what DocEvents get created.
But for this, and any other exceptional cases, consider having the AD or secretariat add a comment to the history at the time something unusual is happening to help leave a clear story for future readers.
Describe the issue
Recently, there was a document (draft-ietf-emailcore-rfc5321bis) that had two LCs because the first LC did not receive enough directorate reviews.
When I received the 2nd LC review request, I withdrew the first LC assignment and closed the first LC review request, and then assigned the new LC review. This can be seen in the histories of the individual review requests:
https://datatracker.ietf.org/doc/draft-ietf-emailcore-rfc5321bis/reviewrequest/20505/
https://datatracker.ietf.org/doc/draft-ietf-emailcore-rfc5321bis/reviewrequest/20629/
But this is not clear in the document history, which shows the following and makes it appear that there was no following assignment:
Code of Conduct
The text was updated successfully, but these errors were encountered: