Recipes vs. Looms vs. pipelines

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Arbash Meinel wrote:
> AIUI, being able to share pipelines is not one of your goals.

Pipelines can already be shared with the sync-pipeline command.

>> With looms, you get a huge proliferation of threads.  I think the only
>> real difference is that threads tend to be less visible than branches.
> 
> True, though this is significant in itself. (possibly solved by
> colocated branches, but visibility of branches is a genuine UI issue.)

Agreed.

> Creating something that makes it easier to get a change integrated into
> upstream, and then reflected back in your workspace seems a lot better
> statement.

Okay, I can agree with that.

> You can get close if we made cherrypicking really smart, but I'm not
> sure how smart you can make it, or really what that design looks like.

Even something only as smart as 'tla replay' would be a great improvement.

> A
> DAG based loom/pipeline is something relatively easy to articulate. As
> it is what I do today with a pure-branch based flow without the
> 'up-thread'/'pump' helpers.

Right, and in this vein, package branches start to look a lot like
integration branches.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkspWuIACgkQ0F+nu1YWqI3WLgCfXd7JjOvz3d4leL5RnWtYMvRi
3pkAnRIZbPl4XQWOiXR78AT/xgLH3mLS
=a49E
-----END PGP SIGNATURE-----