Comment 10 for bug 87012
Revision history for this message
| Colin Watson (cjwatson) wrote Re: [Bug 87012] Re: Cannot start developing next ubuntu release before the prior one is released | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
On Mon, Dec 19, 2011 at 07:33:24PM -0000, Robert Collins wrote:
> So, I think it needs some assessment of the impact on soyuz plumbing - I
> suspect there are some hard coded facilities to fix.
Indeed. This is certainly a process optimisation rather than anything
essential, at this point (given the set of workarounds we've
established); I wouldn't want to compromise correctness or features
elsewhere for this.
> In short though, AIUI, you want:
> - a non-frozen distroseries folk can upload to
> - that doesn't become trunk.
> - and starts off as a clone of the current trunk in terms of content
> - and can have (perhaps automatically?) new packages in trunk copied into it.
Right.
If and when somebody gets to this, we should think about how to present
the case where history diverges after the initial clone. We might just
be able to deal with that manually, and that would probably be
acceptable, but maybe there are better ways too. I also don't know the
exact semantics of the package ancestry stored in Soyuz and what ought
to happen to it in such a case.