UDD @ Portland
robert.collins at canonical.com
Thu Feb 11 02:59:58 GMT 2010
On Thu, 2010-02-11 at 15:42 +1300, Tim Penhey wrote:
> Changing looms to use co-located branches seems like a win to me.
> This would
> also bring looms and pipelines closer. I'd love to see a unified
> model here.
looms and pipelines have very different goals:
- looms aim to manage *and version* a collection of
usually-orthogonal-things with no defined merge order (what upstream
accept, they accept). And many things will never go upstream (e.g.
branding issues, workarounds for other platform issues). Specifically
looms have no intrinsic desire or need for fully-merged pipes, and a
need to let people collaborate on the structure of the loom.
- pipelines aim to let individual developers factor out different
aspects of a feature they are working on, to ease review and provide
clarity about development; they need fully merged to be the normal
situation, don't generally need cherrypicking, and have no need for the
structure of the pipe to be versioned.
I'm keen to share more code with pipelines, but they really are
different things, and I think it's likely harmful to both to push to
hard on them to become similar.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/ubuntu-distributed-devel/attachments/20100211/c2dddb14/attachment-0001.pgp
More information about the ubuntu-distributed-devel