Recipes vs. Looms vs. pipelines
Aaron Bentley
aaron at canonical.com
Wed Dec 16 19:20:04 GMT 2009
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Barry Warsaw wrote:
> When I'm developing bug fix or feature branches, I
> always like to have the devel branch as the bottom thread in my loom. Note
> too though that I want control over when I update the bottom thread
> independently of when I update the devel branch.
What advantages does that gives you? Do you find you miss those when
working on non-loom branches?
> This is something that feels more natural to me in looms than in pipelines.
bzr-pipeline is meant to allow you to use your normal development habits
as much as possible. In fact, a normal branch is also a pipeline with a
single pipe. When you are normally working on a normal branch, the lack
of an upstream pipe should feel perfectly natural, so why does it feel
less natural when you add a second pipe?
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkspMuAACgkQ0F+nu1YWqI3aUwCfQ0XdB0FiJJ4WMtlxjaWFvvs9
PfwAn2id3LPcOsZvtILPczLpM4Ga2R2C
=mK3N
-----END PGP SIGNATURE-----
More information about the ubuntu-distributed-devel
mailing list