deployment report should fail revisions in stable containing undeployed db changes
Bug #845464 reported by
Stuart Bishop
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned | ||
qa-tagger |
Triaged
|
High
|
Unassigned |
Bug Description
A revision in launchpad/stable should be flagged as bad if it contains database changes that have not previously landed in launchpad/
'database changes' means any change to database/
summary: |
- daployment report should fail revisions in stable containing undeployed + deployment report should fail revisions in stable containing undeployed db changes |
Changed in qa-tagger: | |
status: | New → Triaged |
importance: | Undecided → High |
To post a comment you must log in.
Once this is done, the losas can remove the PQM guard blocking database landings on launchpad/devel. This will allow devs to merge db-devel into devel rather than requiring losas to do it.