It is too easy for chairs to miss the instructions to use the Request Publication button rather than manually setting WG state #1418
Comments
|
@rjsparks@nostrum.com uploaded file This is not enough |
|
@rjsparks@nostrum.com commented See also #1515 |
|
@ted.lemon@nominum.com commented Why not just have the state transition from WG Document->Submitted to IESG for publication do the same thing as pressing the Request Publication button? It seems easy to detect this exception. |
|
@rjsparks@nostrum.com changed status from |
|
@rjsparks@nostrum.com changed resolution from `` to |
|
@rjsparks@nostrum.com commented Fixed in 5ee77ca: Reduce confusion around how to send a document from a WG to the IESG through additional, restrictive, validation on the stream state editing form. Fixes bug #1418. Commit ready for merge. |
|
@henrik@levkowetz.com commented Fixed in f2fed6a: Merged in 5ee77ca from rjsparks@nostrum.com: |
resolution_fixedtype_defect| by rjsparks@nostrum.comAs a result, IESG state doesn't get created, and the chairs and ADs become confused.
The form needs to still allow the state to be set manually (to correct errors), but it needs to be stronger in pointing to the button. Perhaps the button should moved to or copied to this state editing page?
Issue migrated from trac:1418 at 2022-03-04 03:45:32 +0000
The text was updated successfully, but these errors were encountered: