* Skip IANA - Review Needed and Version Changed - Review Needed changes from
IANA as it turns out that the Datatracker is the authoritative source on
these states. Also improve logging so that the raw JSON from IANA is
dumped, the parsed JSON on imported changes is dumped and we write to
syslog before starting a sync script in the notification view.
* Only add charter state change link when chartering, it doesn't make sense
for an approved charter. Fixes#861.
* Don't display group.comments on the charter document page. Apparently
group.comments have been used by the Secretariat in the past for
chartering comments, but it's not possible to edit the field and the whole
thing doesn't make sense from a modelling perspective - a feature like
this should probably use the note field on the charter. Fixes issue
#1048.
* Don't crash if an attachment has been created already, just reuse it -
this case shouldn't actually happen, but apparently sometimes does,
probably due to a concurrency issue
* Add link to charter pages from the milestones editing page (besides the
cancel button), fixes#1044.
* Special-case proposed working groups with respect to milestones, they get
the charter milestones on the WG charter page rather than the current set
* Show approved milestones on /doc/charter-xyz/ page if the charter is
approved instead of only showing proposed milestones for proposed charters
- Legacy-Id: 5812
Note: SVN reference [5794] has been migrated to Git commit a603b8e056
Note: SVN reference [5800] has been migrated to Git commit 0f69f87a56
- Legacy-Id: 5786
Note: SVN reference [5614] has been migrated to Git commit 7e0e027149a37e2fac0b2809e8a18c896f660687
Note: SVN reference [5622] has been migrated to Git commit bde631c87ffd2ce5a93fe3c0559aafef04d23b1f
discrepancies report for seeing differences between the
Datatracker/RFC Editor/IANA, add tests of IANA/RFC Editor integration,
add script for weekly discrepancies emails
- Legacy-Id: 4851
/doc/<doc-name>/charter/ since they now all concern the actual charter
documents rather than the WG (this removes some redundant code).
- Legacy-Id: 4271
Setting user cookies, and settable expires soon and new tags
in id/rfc list.
- Legacy-Id: 2634
Note: SVN reference [2619] has been migrated to Git commit ddd9b6fe4d702af5e9b132621a47f59fe2f36b4e
* 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
belong in the apache document root, and will be served by the
django server if it's being run in test or development mode
according to SERVER_MODE.
- Legacy-Id: 566
in (unless it's a forced login) will be the (incomplete) "my" view.
Username and logout link are in the upper right corner while logged
in.
- Legacy-Id: 163
