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.
- Legacy-Id: 17378
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
Refactor to remove dajaxice.
Modified the URLs that address schedules:
- urls now always start with /agenda, removing the mix of /agenda and /schedule prefixes
- urls to a given schedule include the schedule owner (by email address)
Corrected issue that prevented deleting sessions.
Changed comment mechanism in timeslot_edit.js
Migration to change the email address for (System)
Fixes bug #1426
Commit ready to merge
- Legacy-Id: 8229
Updates and bugfixes to the agenda editing features
* Removes the pattern of using ScheduledSession m2m objects with one of the relationships left as None
* Improves scheduled session state handling
* Simplifies sending email to scheduled session requestors
* Improved timeslot purpose and room editing
* Improved access controls to editing forms
* Better test coverage for the meeting views
* Improvements to the javascript driven by prototyping automated tests
* Better initialization of a new meeting
On the session request form:
- Allows specifiying room resources (projectors, meetecho)
- Allows specifying what people must be present
On the schedule editing page:
- correctly calculates conflict levels
- displays conflicts in and out of each session separately
- italicizes BoFs
- shows resource and people conflicts
Adds automated placement as a management command
- Legacy-Id: 7628
Note: SVN reference [7561] has been migrated to Git commit 1221f79af9
* Removes the pattern of using ScheduledSession m2m objects with one of the relationships left as None
* Improves scheduled session state handling
* Simplifies sending email to scheduled session requestors
* Improved timeslot purpose and room editing
* Improved access controls to editing forms
* Better test coverage for the meeting views
* Improvements to the javascript driven by prototyping automated tests
* Better initialization of a new meeting
On the session request form:
- Allows specifiying room resources (projectors, meetecho)
- Allows specifying what people must be present
On the schedule editing page:
- correctly calculates conflict levels
- displays conflicts in and out of each session separately
- italicizes BoFs
- shows resource and people conflicts
Adds automated placement as a management command
Commit ready for merge.
- Legacy-Id: 7561
SimpleUrlTest tests to work with fake data and expand them a bit (they
are still pretty basic), rewrite the agenda editing tests to work with
the small generated fake data, delete those tests that are trivial or
only testing fixture facts as opposed to actually exercising the code,
combine some of them, expand most to actually check the returned JSON
and generally clean up the copy-paste mess of incorrect comments and
incorrect POST data.
At this point, no tests are using the real data base test machinery,
so one can run the full test suite with just
python manage.py test --settings=settings_sqlitetest
This takes about 72 seconds one a 2.4 GHz Intel Core 2. The
test-crawler and other real data tests take somewhat longer, though.
- Legacy-Id: 7069
