Merge lp:~cjwatson/launchpad/git-export-mp-collections into lp:launchpad
Status: | Merged |
---|---|
Merged at revision: | 17549 |
Proposed branch: | lp:~cjwatson/launchpad/git-export-mp-collections |
Merge into: | lp:launchpad |
Diff against target: |
249 lines (+153/-23) 6 files modified
lib/lp/_schema_circular_imports.py (+9/-0) lib/lp/code/interfaces/gitref.py (+25/-11) lib/lp/code/interfaces/gitrepository.py (+24/-11) lib/lp/code/model/gitrepository.py (+1/-1) lib/lp/code/model/tests/test_gitref.py (+47/-0) lib/lp/code/model/tests/test_gitrepository.py (+47/-0) |
To merge this branch: | bzr merge lp:~cjwatson/launchpad/git-export-mp-collections |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
William Grant | code | Approve | |
Review via email: mp+261206@code.launchpad.net |
Commit message
Export merge proposal collections on GitRepository and GitRef.
Description of the change
Export merge proposal collections on GitRepository and GitRef.
10:54 <cjwatson> wgrant: Have you thought of any better names for landing_candidates et al? Otherwise I'm inclined to export the current names on the grounds that Tarmac will need them and it's probably least confusing there for them to match Bazaar.
10:55 <wgrant> shuf -n 2 /usr/share/
10:56 <cjwatson> :-P
10:56 <wgrant> The current names aren't obviously worse than the Bazaar equivalents, are they?
10:57 <wgrant> Apart from the repo vs branch stuff, nothing has changed terribly.
10:57 <cjwatson> The current names are identical to the Bazaar equivalents.
10:57 <wgrant> Right, but there's no real reason we have to change them.
10:57 <wgrant> That I can recall.
10:57 <cjwatson> That was my thought.
10:57 <cjwatson> I mean, they suck but they can suck equally.
10:57 <wgrant> It was just a "this bit of Bazaar codehosting is stupid, let's see if we can do it better before stabilising the API"
10:57 <wgrant> And at this point I think the answer is no.
10:58 <cjwatson> Like most things that talk about sources and targets etc., it's very easy to get into directional confusion.
10:58 <wgrant> Yeah
10:58 <cjwatson> Especially for this kind of thing where it's really "merge proposals for which this branch etc. is the source"
10:58 <wgrant> The least confusing thing might almost be to have lp.merge_
10:59 <wgrant> But exporting the existing properties works.
11:03 <cjwatson> lp.merge_proposals has the nice property that we could introduce it later without too much clutter, indeed.