drafts published as RFCs not moved to archive

[ietf-svn-bot]

owner:olau@iola.dk resolution_fixed type_defect | by rcross@amsl.com

---

The document status synchronization with RFC Editor, which is now automated, does not move drafts into the archive directory when they are published as RFCs. This may be related to other tickets which call for a cron script to move documents into the archive directory.

http://wiki.tools.ietf.org/tools/ietfdb/ticket/1164
http://wiki.tools.ietf.org/tools/ietfdb/ticket/1165

From RT #62480
Hello,

I just noticed an oddity today:

RFC 7064 was published in November. But
draft-nandakumar-rtcweb-stun-uri, which it was based on, seems to be
still present in the internet-drafts directory that I mirror from
optimus.ietf.org::internet-drafts using rsync.

Is this a glitch in the scripts for this particular draft, or is there
some larger issue?

Harald Alvestrand

---

Issue migrated from trac:1254 at 2022-03-04 03:33:16 +0000

[ietf-svn-bot]

@olau@iola.dk changed status from new to closed

[ietf-svn-bot]

@olau@iola.dk changed resolution from `` to fixed

[ietf-svn-bot]

@olau@iola.dk commented

---

Fixed in 32874a2:

Move draft files to archive when setting the draft state to RFC,
fixes #1254.

[ietf-svn-bot]

@olau@iola.dk commented

---

I've committed a fix to the djangoport branch which should go live soon.

Regarding cron job: we do actually have one already doing regular maintenance, the meat is in clean_up_draft_files in doc/expire.py. There's even a pretty thourough test for it. It would probably be a good idea to teach it about these cases, but I think it requires someone with access to the server and a better idea of where things should end up to take a look first. :)