creating mps for collisions isn't helpful
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu Distributed Development |
Confirmed
|
High
|
Jonathan Riddell | ||
Bug Description
At the moment, when the package-importer discovers a divergence between its imports and the package branch, it creates an mp
This has a few problems:
* The enormous mp is not very useful to the Ubuntu developers who receive it, and probably just noise.
* The real problem is not to resolve this conflict, but to improve the udd package-importer so that it does not generate non-semantic conflicts.
I don't know all of what is needed to avoid these conflicts, but we can at least start getting a better picture of what's going on, by:
* logging the conflicts
* perhaps reporting them on the status page, perhaps matched up to bugs
* looking into what needs to be done to reduce them
examples:
<https:/
https:/
https:/
https:/
| Changed in udd: | |
| assignee: | nobody → canonical-bazaar (canonical-bazaar) |
| Robert Collins (lifeless) wrote Re: [Bug 766757] [NEW] creating mps for collisions isn't helpful | #1 |
| Martin Pool (mbp) wrote | #2 |
| Martin Pool (mbp) wrote | #3 |
| Changed in udd: | |
| assignee: | canonical-bazaar (canonical-bazaar) → Jonathan Riddell (jr) |
| description: | updated |
| Martin Pool (mbp) wrote | #4 |
The general idea was that conflicts would only be happening when a
developer pushes to the branch and a different developer pushes
directly to the archive. If we're getting massive merge proposals, I
suggest that figuring out why that is happening is important.
The reason for using mps is that:
- developers didn't want work they have pushed to the branch lost
- bugs with attachments seemed ugly and less user friendly.