your thoughts wanted on bzr team UDD focus

[Aaron Bentley]

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

Martin Pool wrote:
> What I'm trying to get at here is the next level of detail of what we
> can be doing to help with bzr builder, imports and bugs?  If a major
> cause of failing imports is lack of git submodule support, that would
> be a strategic thing for us to resolve.

If you look at mwhudson's research:

https://devpad.canonical.com/~mwh/values-sorted.txt

Only five failures are due to the lack of submodule support.

However, we can ignore svn issues because we're switching to bzr-svn.
(We hope that will solve many of our problems, but whichever problems
remain will be *different*)

So there are a lot of failures on that scale, and any of them would be
worth solving.  Some of the errors are pretty unclear, like this one:

OSError: [Errno 17] File exists:
'/srv/importd.launchpad.net/data/worker-for-branch-25632/bzr_working_tree/.bzr'
 pypi-mirror-trunk-logtail.txt

> What do you think is most
> useful to help with daily builds or imports?

For bzr-builder
 - Support for recipe inheritance
 - Support for copying just the debian directory out of an existing
   package branch
 - Support for copying just the debian directory, without any of the
   patches out of an existing package branch, to enable upstreams to
   package their exact code.

For imports
 - I would just pick a problem off the list and investigate.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAksdsKgACgkQ0F+nu1YWqI00ogCgiVFRzVQHlJriyOV+U738Lywj
6pQAn3pfoFzttvR5EI6vF52MVAmc3u3l
=tAhH
-----END PGP SIGNATURE-----