search

ietf-tools / datatracker

The day-to-day front-end to the IETF database for people who work on IETF standards.
https://datatracker.ietf.org
BSD 3-Clause "New" or "Revised" License
607 stars 371 forks source link

Drafts under ISE (or any other stream manager review) are not protected from expiry without manual intervention #1653

Open ietf-svn-bot opened 9 years ago

ietf-svn-bot commented 9 years ago

keyword_sprint type_defect | by rjsparks@nostrum.com

Currently, the secretariat has to manually set a tag on a document when it enters conflict review (by toggling a check-box on /secr/drafts/(draftname)/edit).

Instead, this should happen automatically when a conflict review is requested.

Issue migrated from trac:1653 at 2022-03-04 04:33:08 +0000

ietf-svn-bot commented 8 years ago

@rjsparks@nostrum.com changed keywords from ` tosprint`

ietf-svn-bot commented 6 years ago

@rjsparks@nostrum.com commented

This tag (rfc-rev) is probably not getting set at all given the secretariats modern workflow, and, if so, drafts newly placed in ISE review aren't being protected from expiry. Is that OK?

ietf-svn-bot commented 4 years ago

@rjsparks@nostrum.com changed status from new to accepted

ietf-svn-bot commented 3 years ago

@brjb2020@gmail.com changed status from accepted to closed

ietf-svn-bot commented 3 years ago

@brjb2020@gmail.com set resolution to fixed

ietf-svn-bot commented 3 years ago

@rjsparks@nostrum.com changed status from closed to reopened

ietf-svn-bot commented 3 years ago

@rjsparks@nostrum.com removed resolution (was fixed)

ietf-svn-bot commented 3 years ago

@rjsparks@nostrum.com changed status from reopened to accepted

ietf-svn-bot commented 3 years ago

@rjsparks@nostrum.com commented

sorry for the noise - mitigating some incorrect changes

ajeanmahoney commented 3 months ago

The only place the rfc-rev tag is mentioned in the code currently is in expire.py. It doesn't seem to be set anywhere.