* announcements -> ann
* liaisons -> liaison
* idindex -> drafts
* mailinglists -> list
I checked the tests and used a link checker locally, so hopefully
the fallout will be minimal.
- Legacy-Id: 657
served by the mailing list form so bookmarks to them are extremely
unlikely.
Remove trailing "?" from /idtracker/ entry; the redirect tool
strips off empty query strings.
Add ?cat=bugs to the send_email entry so the redirect will pass.
Skip the redirect test for the ballot, since there's an extra
(unused) query argument, filename=.
Add in all the query args that will get passed through the
redirect when searching for bgp-m, to make sure that they work
and to make the redirect test pass.
- Legacy-Id: 609
are the same as their cgi counterparts. Differences:
* The sections are ordered differently; the cgi has Active, Published, Expired, Withdrawn; the django has Active, Expired, Published, Withdrawn by IETF, Withdrawn by Submitter. Since the explicit ordering by the cgi was why it missed the "Withdrawn by Submitter" documents, I chose to keep the database-influenced ordering.
* The revision numbers for published documents are of the version that was published, not of the tombstone.
- Legacy-Id: 590
Remove debugging and leftover bits from related_docs function.
Handle unexpected exceptions in related_docs related to schema
oddities described in #98:
* There might not be a row in the RFC table for a given rfc_number of an I-D
* There might be multiple documents published as the same RFC
Don't skip anything when recursing from our equivalents of
get_rfcs_obsoleted and get_rfcs_obsoleted_by.
- Legacy-Id: 521
is still a work in progress. I've been using
draft-ietf-dnsext-dnssec-protocol as a test case; related_docs()
returns the same 137 documents as the cgi code but some of the
relationships are different. Right now, the skip argument is
ignored.
- Legacy-Id: 246
