this week in ~canonical-bazaar

[Vincent Ladeuil]

Standup 2011-12-13

jelmer
------

* finished a few WIP MPs
 + obsolete_pack removal the famous "pi" "pi" bug <http://pad.lv/314314>
 + mkdir -p (with mgz)
* Submitted feature flags support
* Released bzr-svn 1.1.2 for 2.5 compatibility
* Uploaded new versions of HPSS-get-inventories
* Released bzr-gtk 0.103.0
* Avoid loading XML modules when working on 2a repositories (little bit
  less loading time)
* Loaded foreign plugins by default in Launchpad (so git/svn/hg revids
  are shown in loggerhead)
* Add support for recipe format 0.4 in Launchpad
* Add and use matcher to make sure HPSS calls don't include VFS requests
* released 2.5b4 debian packaging

mgz
---

* qbzr AttributeError on 'is_ignored' in treewidget <http://pad.lv/557603>
* export_pot duplicate handling from feedback on 2.5b4 freeze pot changes
* tried and failed to sort out runtime libraries mess on windows
  <http://pad.lv/881203>
* built 2.5b4 windows installers
* ascii is a bad default filesystem encoding <http://pad.lv/794353>
* Proposed merge for previously discussed python-oops-tools issue
  <http://pad.lv/891186>
* environment variables are not decoded properly <http://pad.lv/832028>

next:

* Document testing for SxS problems
* Work out how to fix stacked bzr branches on launchpad

vila
----

* patch pilot, review queue in reasonable shape and still is.
* more config bugs fixed <http://pad.lv/832064>
* froze 2.5b4
* udd:
** better handling for killing long imports <http://pad.lv/899308>,
   <http://pad.lv/899231>
** nexuiz-data is still problematic even running for 3 days, last output
   occurring roughly after 1 hour of processing
** migration to the new bzr config scheme, package specific config is
   now available (http://pad.lv/899308, http://pad.lv/902125 and
   associated followups), lots of basic tests added, running mass-import
   locally for smoke tests becomes affordable.

NEXT:
* announce 2.5b4
* migrating more config options
* <http://pad.lv/874153> add a specific -E flag that skips the failing
 test by default and keep it active on babune so we separate the
 fallouts for all downstreams from keeping track of the issue internally
* properly explain what is possible with the new config design and how
  to do it.