Merge lp:~abrody/launchpad/https-mirror-dbchange into lp:launchpad/db-devel
Proposed by
Andy Brody
Status: | Rejected | ||||
---|---|---|---|---|---|
Rejected by: | Colin Watson | ||||
Proposed branch: | lp:~abrody/launchpad/https-mirror-dbchange | ||||
Merge into: | lp:launchpad/db-devel | ||||
Diff against target: |
19 lines (+15/-0) 1 file modified
database/schema/patch-2209-99-0.sql (+15/-0) |
||||
To merge this branch: | bzr merge lp:~abrody/launchpad/https-mirror-dbchange | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Colin Watson (community) | Approve | ||
Review via email: mp+362902@code.launchpad.net |
This proposal supersedes a proposal from 2019-02-02.
Description of the change
Add column DistributionMir
To post a comment you must log in.
Unmerged revisions
- 14020. By Andy Brody
-
Add DistributionMir
ror.https_ base_url column.
This needs to be re-prepared as a branch from lp:launchpad/db-devel, and proposed as a merge into lp:launchpad/db-devel. We can't land database patches against devel directly, except in a few specialised circumstances. Furthermore, the code branch (lp:~abrody/launchpad/https-mirror) may not declare the DB branch as a prerequisite; it must instead be a separate branch that doesn't itself contain the DB changes. This is all because database and code updates are deployed from separate branches; see https:/ /dev.launchpad. net/PolicyAndPr ocess/DatabaseS chemaChangesPro cess.