No subject

to do are:

 * get more code imports working -- investigation of failure causes is
continuing
 * support imports of git submodules or svn externals -- this is not moving yet

At the moment we're mostly doing consolidation work after 2.0:
continuing to pull on performance threads (2.1 should be substantially
faster and use less memory), fixing bugs, improving documentation, and
making community contribution more fun.  This is very satisfying and
going well, but we may need to shift focus to more specifically
strategic things.

I'd like that bug work to be guided by UDD requirements.  So feel free
to either ask here, or put the 'affects-udd' tag onto our bugs, or ask
on irc or the Bazaar list.  I'd say that tag should count as about a
+3 to hit, or in other words an upgrade of one Importance level.

My sense is that getting submodule/external imports going by February
is not out of the question but might be a stretch to do it safely.
(More data welcome.)  And it seems also that for the initial rollout
of UDD it would be ok to do it on trees that don't use
submodules/externals, but it will of course block widespread use.

So, UDDers:

 * are there other things that should be on this map, either bugs or features?
 * how do you feel about the relative importance of those features vs
bugs or performance?
 * how crucial is it to get submodule/external support in 2.1?

Thanks
-- 
Martin <http://launchpad.net/~mbp/>