User Tools

Site Tools


current_file_mgmt

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
current_file_mgmt [2026/08/03 16:01] – noted that this info is becoming legacy practice jmahoneycurrent_file_mgmt [2026/08/03 16:01] (current) – formatting jmahoney
Line 2: Line 2:
  
 **Note that the RPC is moving away from the following process, which had been in place for many years.** The RPC is now placing documents in GitHub repos, but editors are still sharing documents and diff files with authors via the legacy file management system. **Note that the RPC is moving away from the following process, which had been in place for many years.** The RPC is now placing documents in GitHub repos, but editors are still sharing documents and diff files with authors via the legacy file management system.
 +
 +
 +----
 +
  
 When the RPC receives an email message announcing that a document has been approved, a member of the RPC runs a script to add that document's files to an internal directory on rfcpa.rfc-editor.org where all editing work takes place. The document's filename contains the same version number as the document that was approved. That is, if draft-ietf-foo-bar-03 was approved, then its filename remains draft-ietf-foo-bar-03.xml as it is being worked on. When the RPC receives an email message announcing that a document has been approved, a member of the RPC runs a script to add that document's files to an internal directory on rfcpa.rfc-editor.org where all editing work takes place. The document's filename contains the same version number as the document that was approved. That is, if draft-ietf-foo-bar-03 was approved, then its filename remains draft-ietf-foo-bar-03.xml as it is being worked on.
current_file_mgmt.txt · Last modified: by jmahoney

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki