This provides support for IRSG ballots, similar to the IESG ballots support which has been in use for quite some time. The IRSG ballots differ from IESG ballots in a number of ways, described in detail in the RFP and SoW for this work and implemented here.
- Legacy-Id: 17164
Strip the HTML tags around the new values in the mail produced by email_iesg_processing_document. Also, provide the previously missing URL at the end of the message. Fixes 2455.
- Legacy-Id: 14657
Note: SVN reference [14655] has been migrated to Git commit 6ea0881a89
- Legacy-Id: 14411
Note: SVN reference [14406] has been migrated to Git commit 967ece7e7d
Note: SVN reference [14410] has been migrated to Git commit 660c81c272
Check downref registry when producing Last Call text. Fixes#2069.
- Legacy-Id: 13210
Note: SVN reference [13205] has been migrated to Git commit aa7ed23cda
Generate a message to Secretary and IESG when AD changes a draft state
to 'Approved'. Fixes issue #796.
- Legacy-Id: 11714
Note: SVN reference [11687] has been migrated to Git commit ae87e84610
Note: SVN reference [11710] has been migrated to Git commit 65bb1f2738
The IESG Telechat Agenda now shows "(Has RFC Editor Note)" after the I-D
filename if there is an RFC Editor Note associated with the document. This
was added to the html and txt versions of the agenda. It was not added to the
Secretariat view or the Scribe view of the agenda.
For transition, when an AD edits the RFC Editor Note, they need to move the
text from the current writeup into the new field. Returning documents on the
telechat agenda seems to be the biggest opportunity for something to fall
between the cracks. If an event of type "changed_rfc_editor_note' exists, and
the string "RFC Editor Note" appears in the text of the most recent
'changed_ballot_writeup_text' event, then a message is shown that tells the AD
to remove the RFC Editor Note from the writeup.
- Legacy-Id: 10783
Note: SVN reference [10770] has been migrated to Git commit 4b5ac9e09e
Note: SVN reference [10771] has been migrated to Git commit 46589ee421
Note: SVN reference [10772] has been migrated to Git commit c73659e95c
Note: SVN reference [10773] has been migrated to Git commit 2e6633c016
focused on supporting the IRTF better, but also removing some redundancies
(i.e., including group_info.txt instead of duplicating something similar.)
Commit ready for merge.
- Legacy-Id: 10674
Provide information about who has suggested document replaced-by information in the notification email.
This commit fixes bug 1817,
- Legacy-Id: 10440
Note: SVN reference [10425] has been migrated to Git commit ba39077180
The new API requires at least one event and will automatically save a
snapshot of the document and related state. Document.save() will now
throw an exception if called directly, as the new API is intended to
ensure that documents are saved with both an appropriate snapsnot and
relevant history log, both of which are easily defeated by just
calling .save() directly.
To simplify things, the snapshot is generated after the changes to a
document have been made (in anticipation of coming changes), instead
of before as was usual.
While revising the existing code to work with this API, a couple of
missing events was discovered:
- In draft expiry, a "Document has expired" event was only generated
in case an IESG process had started on the document - now it's
always generated, as the document changes its state in any case
- Synchronization updates like title and abstract amendmends from the
RFC Editor were silently (except for RFC publication) applied and
not accompanied by a descriptive event - they now are
- do_replace in the Secretariat tools now adds an event
- Proceedings post_process in the Secretariat tools now adds an event
- do_withdraw in the Secretariat tools now adds an event
A migration is needed for snapshotting all documents, takes a while to
run. It turns out that a single document had a bad foreign key so the
migration fixes that too.
- Legacy-Id: 10101
