Merge lp://staging/~cjohnston/summit/import-bp-status into lp://staging/summit
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Approved by: | Chris Johnston | ||||
| Approved revision: | 534 | ||||
| Merged at revision: | 535 | ||||
| Proposed branch: | lp://staging/~cjohnston/summit/import-bp-status | ||||
| Merge into: | lp://staging/summit | ||||
| Prerequisite: | lp://staging/~cjohnston/summit/render-schedule-tests-utc | ||||
| Diff against target: |
461 lines (+375/-5) 5 files modified
summit/schedule/admin/meetingadmin.py (+1/-0) summit/schedule/migrations/0029_extend_meeting_status.py (+211/-0) summit/schedule/models/meetingmodel.py (+19/-4) summit/schedule/tests/meeting_model.py (+141/-0) summit/schedule/tests/render_schedule.py (+3/-1) |
||||
| To merge this branch: | bzr merge lp://staging/~cjohnston/summit/import-bp-status | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Michael Hall (community) | Approve | ||
|
Review via email:
|
|||
Commit message
Add support for additional blueprint statuses
Description of the change
With the recent change to LP (YAY!) we are getting an export of all blueprints that are marked as approved for a sprint. With this comes some issues that we need to overcome.
1) set proper status based upon the status from LP
2) Deal with superseded and obsolete blueprints
The things I did in this MP:
- Added the new status options to the meeting.status field
- Add status to meeting admin page
- Add support to lpupdate for marking a meeting from a blueprint that is either Superseded or Obsolete as 'REMOVED' so that it will not be scheduled
- Added support to lpupdate so that a meeting from a blueprint which was marked as Superseded or Obsolete, however is no longer marked as such will have its status changed from 'REMOVED' to 'APPROVED' and allow it to be scheduled yet again
- Tests -- yippie
| Tarmac WebDev (tarmac-webdev) wrote | # |
Looks good