Hi all,
On 7/8/25 11:05 PM, Martin Thomson wrote:
On Wed, Jul 9, 2025, at 01:15, Jean Mahoney wrote:
Entry into the AUTH state is not dependent on the completion of a
previous queue state. A document exits AUTH state when the questions
have been answered, and back to the previous state the document was in.
For example, EDIT -> AUTH -> EDIT.
I think that there is problem here, particularly as it relates to this state
(from the author tools page Jay cited):
Once a document is approved, it enters the publication queue and is managed by
the RFC Production Center (RPC). From this point on, the RPC has change control
of the document.
And then this from the new message about the AUTH state:
* If you need/want to make updates to your document, we encourage you to
make those changes and resubmit to the Datatracker.
The question of who holds the authority to change the document is key. I've
always operated on the basis that author copies are no longer the primary and
the RPC holds the pen. Some clarity would be appreciated. Is AUTH handing
back control? How does that work when EDIT has already resulted in changes?
[JM] For this experimental intake process, an author can update the
document, and these updates won't cause a conflict with the document in
the queue because the RPC will wait for a response from the author
before editing the document. (The doc is first placed into EDIT state
only so the RPC can collect SLA stats.)
If the author submits a new version, the RPC will review it for
technical updates. If an update appears to be technical, we will ask a
stream manager to review before starting work on the new version.
We will be collecting statistics on how often an author submits a new
version and whether the new version requires stream approver review due
to technical changes, and we will adjust the process if we see too many
of these kinds of updates.
Best regards,
Jean
_______________________________________________
rfc-interest mailing list -- [email protected]
To unsubscribe send an email to [email protected]
