Store Auth48 URL as DocumentURL and display in RFC-Editor state. Migrates old data when possible. Alternative to 17563. Fixes#2722.
- Legacy-Id: 18166
Note: SVN reference [18157] has been migrated to Git commit fff927b085
session when rescheduling a session after the schedule is made the
official meeting schedule.
Show both cancelled and rescheduled sessions as tombstones in the new
meeting schedule editor.
Add support for showing rescheduled tombstones in the meeting agenda
views.
Adjust the Secretariat session tool so that it's not possible to
(re)cancel cancelled or rescheduled tombstones.
- Legacy-Id: 18108
references directly in the database as HTML.
Rework the label update migration to take this into account (can be
rerun by running "ietf/manage.py migrate name 0011 --fake" first).
Add a little bit of support for the recently added constraints types -
the JS does not hint about them, but they do show up without looking
silly.
- Legacy-Id: 18033
Add used_roles to Group and default_used_roles to GroupFeatures. Dynamically build the group edit form to provide a field for all used_roles. Fixes#2785 and #2572. Partially addresses #2160.
- Legacy-Id: 17960
Note: SVN reference [17908] has been migrated to Git commit 2862727d02
Allow IAB programs to use normal meeting mechanics. Fixes#2970.
- Legacy-Id: 17773
Note: SVN reference [17764] has been migrated to Git commit fb8e5c6842
Turned autoescape off for another email fragment template (production database has also been changed). Fixes an issue where test_assign_reviewer() would sometimes fail due to html-escaped characters in email text.
- Legacy-Id: 17745
Note: SVN reference [17711] has been migrated to Git commit 8ec9e1cf77
upcoming automatic scheduling assistance:
. Added a management command to create a dummy IETF 999 meeting.
. Added display of new constraints and joint sessions to agenda builder
interface.
. The new timerange, time_relation and wg_adjacent constraints, along with
the joint_with_groups option, are now reflected in the special requests
field. This allows them to be taken into account while scheduling
sessions.
. Clarified the wording in the session request form regarding conflicts with
BOFs.
. Added support for structured entry and storage of joint sessions in
meetings:
- Also adds additional tests for the SessionForm
- Fixes a javascript error in session requests for non-WG groups,
that could cause incorrect form behaviour.
- Expands the tests added in [17289] a bit.
. Added support for the timerange, wg_adjacent and time_relation constraints.
This adds three new constraints to the database and relevant UIs:
- timerange: "This WG can't meet during these timeframes"
- wg_adjacent: "Schedule adjacent to another WG (directly following,
no breaks, same room)"
- time_relation: schedule the two sessions of one WG on subsequent
days or with at least one day seperation
- Legacy-Id: 17605
Note: SVN reference [17289] has been migrated to Git commit a227813dc5
for displaying violated constraints in the new schedule editor, with
the old of a new field, ConstraintName.editor_label.
Add support for displaying room capacity violations.
Add support for selecting a session and displaying information about
it similar to the existing scheduling editor.
Add support for sorting unassigned sessions.
Clean up markup and styles a bit, and fix some bugs.
Expand HTML-based test and add JS test that exercises the
Javascript-based functionality.
Switch to using Chrome driver instead of PhantomJS since the HTML
engine in PhantomJS is apparently too old to support the constructs in
the new schema editor.
Add a workaround for LiveServerTestCase clashing with IetfTestRunner
fixture loading.
- Legacy-Id: 17519
Move charters for replaced groups to a new replaced state. Close any outstanding ballots on them. Fixes#2889, #2873, and #1286.
- Legacy-Id: 17420
Note: SVN reference [17396] has been migrated to Git commit 79bb245f8a
Make internal review email about an RG use the IRSG instead of the IESG in text and addresses. Fixes#2881.
- Legacy-Id: 17307
Note: SVN reference [17288] has been migrated to Git commit 4cce1b5e08
This adds three new constraints to the database and relevant UIs:
- timerange: "This WG can't meet during these timeframes"
- wg_adjacent: "Schedule adjacent to another WG (directly following,
no breaks, same room)"
- time_relation: schedule the two sessions of one WG on subsequent
days or with at least one day seperation
- Legacy-Id: 17289
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
* Renamed Meeting.agenda to Meeting.schedule together with a bunch of related
internal things
* Moved Session.status, .requested, and .requested_by to a new SchedulingEvent.
* Turned sessions into regular sessions and non-sessions into misc.
sessions in the UI and code to avoid ambiguity.
This doesn't change the data in the DB except for uses of
TimeSlotTypeName where 'session' is now 'regular'.
- Legacy-Id: 17153
sessions in the UI and code to avoid ambiguity.
This doesn't change the data in the DB except for uses of
TimeSlotTypeName where 'session' is now 'regular'.
- Legacy-Id: 17128
This abstracts queue management, making it possible to implement different
policies for each team. It provides two concrete policies:
RotateAlphabeticallyReviewerQueuePolicy, which rotates an alphabetically
ordered reviewer list with consideration for skip indications, and is the
default policy; and LeastRecentlyUsedReviewerQueuePolicy, a simple
least-recently-used policy. Also see issues #2721 and #2656.
- Legacy-Id: 17121
Fix#2123 - Use a DBTemplate when a review assignment is mailed.
The message sent to a reviewer when a new review is assigned to them,
is now taken from a DBTemplate, allowing it to be customised
per team. This includes a migration to create a default template,
which looks the same as before.
- Legacy-Id: 16928
Note: SVN reference [16921] has been migrated to Git commit 9df5839874
The message sent to a reviewer when a new review is assigned to them,
is now taken from a DBTemplate, allowing it to be customised
per team. This includes a migration to create a default template,
which looks the same as before.
Commit ready for merge.
- Legacy-Id: 16921
Don't copy early reviews to ietf_last_call by default.
- Legacy-Id: 16884
Note: SVN reference [16825] has been migrated to Git commit 54c221b6e03b573041600645d34316292e058d66
Refs #2277 - Send daily reminders of overdue reviews to secretaries
- Legacy-Id: 16839
Note: SVN reference [16765] has been migrated to Git commit cc64992204
Fix#2354 - Make review_completed configurable per team and review type
This includes a migration to change mailtrigger slugs to be up to 64
characters instead of 32, as some slugs would not fit and require clunky
abbreviations.
A data migration creates triggers for existing teams, and they are also
created on the fly if a trigger does not exist yet, providing a safe
fallback for new review teams. The review_completed mailtrigger serves
as the template for new triggers.
This commit also includes tests for gather_address_lists(), as none
existed.
- Legacy-Id: 16794
Note: SVN reference [16680] has been migrated to Git commit 1390ae073c
Fix#2328 - Use mailtriggers to find destinations in review app
As the review app has several conditionals that don't fit
entirely well within mailtriggers, the templates use a bit
of extra context to figure out who exactly to include. This also
extends the tests for review, to check for correct recipients.
It also adds a tiny feature to mailtrigger to entirely exclude
certain addresses, as required by the review-generated mails.
- Legacy-Id: 16793
Note: SVN reference [16672] has been migrated to Git commit 88b7b45b0e
This includes a migration to change mailtrigger slugs to be up to 64
characters instead of 32, as some slugs would not fit and require clunky
abbreviations.
A data migration creates triggers for existing teams, and they are also
created on the fly if a trigger does not exist yet, providing a safe
fallback for new review teams. The review_completed mailtrigger serves
as the template for new triggers.
This commit also includes tests for gather_address_lists(), as none
existed.
Commit ready for merge.
- Legacy-Id: 16680
As the review app has several conditionals that don't fit
entirely well within mailtriggers, the templates use a bit
of extra context to figure out who exactly to include. This also
extends the tests for review, to check for correct recipients.
It also adds a tiny feature to mailtrigger to entirely exclude
certain addresses, as required by the review-generated mails.
Commit ready for merge.
- Legacy-Id: 16672
primary keys from character strings to integers, and makes corresponding code
changes.
This was prompted by database limitations discovered when trying to make
DocAlias use a m2m document field; with 255 long strings as primary keys for
Document and DocAlias this violated the MySQL database limitations.
Changing the primary keys to integers should also improve efficiency.
Due to the data migrations which create the new integer primary keys and adds
corresponding integer foreign keys matching the previous string foreign keys
in all tables having foreign keys to Document and DocAlias, some of these
migrations take a long time. The total set of migrations are expected to have
a runtime on the order of 2 hours.
- Legacy-Id: 16237
Remove some clutter from I-D upload page. The information was mived to the Instructions tab, but a higligh to the Note Well and BCP 78 was added. Fixes#2057.
- Legacy-Id: 16151
Note: SVN reference [16144] has been migrated to Git commit 37851b9742
Notify the RFC Editor when an RFC Editor note is changed after a draft has been approved. Fixes#2440.
- Legacy-Id: 15729
Note: SVN reference [15698] has been migrated to Git commit 43374969f6
Tune the recipients when a teams settings or a reviewer indicate ADs should be notified about a review.
- Legacy-Id: 15682
Note: SVN reference [15677] has been migrated to Git commit 24b83240e0
Let review teams opt in to poking a responsible AD when unhappy reviews are submitted. Fixes#2544.
- Legacy-Id: 15678
Note: SVN reference [15675] has been migrated to Git commit c7bf147b1d
Corrected some DocTypeName entries' prefix value. Made the search code more robust against DocTypeName objects that have an empty prefix value. Fixes#2599.
- Legacy-Id: 15604
Note: SVN reference [15601] has been migrated to Git commit 22d459362aec2a06854a515fbcebfec54e8a6e69
in a database table:
- Added a GroupFeatures model to the group models, and removed the old
features.py
- Added a agenda type for future use in showing different group types on
different agendas.
- Renamed the group feature has_materials to has_nonsession_materials.
- Added API resources and admin support for the new tables.
- Added a Directorate (with reviews) group type as complement to
Directorate, to distinguish between directorates with and without reviews.
- Adjusted tests as needed.
- Updated the fixtures, and fixed the generate_fixtures script to include
the new AgendaTypeName objects.
There still exists about 70 instances of code comparing the group type
with a list of types; most of these should probably be replaced with new
features, instead, to make it possible to add new group types through the
database table, rather than having to edit the code. That was the purpose
of this refactoring from the start, but the presence of this large number
of comparisons of group type against lists of types defeats the goal until
we add appropriate features and replace the group type list comparisons.
- Legacy-Id: 15316
Send email when the responsible AD for a conflict review is changed. Include the stream manager and stream steering group when the responsible AD changes or when the telechat date changes. Fixes#2497.
- Legacy-Id: 15156
Note: SVN reference [15152] has been migrated to Git commit 6b779e9d4c
Missed adding the migrations. Related to #1963.
Merged in [15119] from rjsparks@nostrum.com:
Change stream state to replaced when an ISE, IAB, or IRTF document
is replaced. Fixes#1963.
- Legacy-Id: 15122
Note: SVN reference [15119] has been migrated to Git commit 1295f1f1d2
Note: SVN reference [15120] has been migrated to Git commit 1c16926ee6
Add the ability to add a comment to a group's history. Fixes#1483.
- Legacy-Id: 14485
Note: SVN reference [14468] has been migrated to Git commit 13e8f8982c
This could be used to point to a document source repository, to extracted
yang module files, document wikis, and other relevant resources.
- Legacy-Id: 14166
addition to the existing 'pyang' checker.
Added modal overlay displays showing the yang check results every place the
yin/yang symbol is shown (red or green) to indicate the presencee and result
of yang checks. Added a Yang Validation: line in the document
meta-information section on the document's page in the datatracker.
Added the result of the xym extaction to the yang check results, to make
extration failures visible.
Added the version of the used xym, pyang, and yanglint commands to the check
results.
Added an action to move successfully extracted and validated modules to the
module library directories immediately on submission.
Added the xym and pyang repositories as svn:external components, rather than
listing them in requirements.txt, as there has been delays of many months
between essential features in the repositories, and an actual release. We may
get occasional buildbot failures if broken code is pulled in from the
repository, but better that than the functionality failure of severely
outdated componets.
Added a new management command to re-run yang validation for active drafts for
which yang modules were found at submission time, in order to pick up imported
models which may have arrived in the model libraries after the draft's
submission. Run daily from bin/daily.
Added a table to hold version information for external commands. The yang
checker output should include the version information of the used checkers,
but seems unnecessary to run each command with its --version switch every
time we check a module...
Added a new management command to collect version information for external
commands on demand. To be run daily from bin/daily.
Added tests to verify that xym, pyang and yanglint information is available
on the submission confirmation page, and updated the yang module contained in
the test document to validate under both pyang and yanglint.
Updated admin.py and resource.py files as needed.
- Legacy-Id: 13630
Allow the nomcom to collect feedback on arbitrary topics. Fixes#2256 and #1846.
- Legacy-Id: 13506
Note: SVN reference [13474] has been migrated to Git commit 4813177086
This completes a good chunk of the downref registry work requested in ticket
#2069. The registry has been imported to the database and can be shown, and
entries can be added to the registry. Addresses issue #2069.
- Legacy-Id: 13190
Note: SVN reference [13181] has been migrated to Git commit f0125634f8