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. -Rob
signature.asc
Description: This is a digitally signed message part
-- ubuntu-distributed-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
