Just a few brief notes about UDD discussions at UDS-N. A lot of this is captured to various degrees in gobby documents and IRC logs at <http://ubottu.com/uds-logs/>, but they're pretty long:
<http://ubottu.com/uds-logs/%23ubuntu-uds-bonaire2.log> * There was a lot of interest in adopting something like the bzr patch pilot process in Ubuntu; it's worked well for us and I'm pleased Rick is willing to give it a go in the different situation of Ubuntu. I hope it goes well. <http://ubottu.com/uds-logs/%23ubuntu-uds-curacao1+2.log> The main discussion about UDD is here, starting about 2010-10-27T16:08, and there are a lot of good things for us to work on, including: * speed of getting source through UDD, considered holistically (including outright speed, needing to fetch from the UK rather than a closer mirror, shallow checkouts, proactive mirroring) * various merge cases that could be better * problems with packages with complex history already in bzr, creating multiple histories Some other observations: * currently used by very much early-adopters * build from recipe quite successful, though still quite young * focus on eliminating tedium * check out grab-udd-merge At the end of that discussion we picked two specific items for the bzr team: * speed * loom support, on lp and within bzr, and connecting them to packaging patches and for Launchpad * build from branch into the main archive * actually execute a merge from a merge proposal * through launchpad. merge from a debian branch into an ubuntu udd branch We did not get around to doing interactive user testing; I'm trying to reschedule that with mrevell. We did get survey responses, and I will send a summary of them soon. -- Martin -- ubuntu-distributed-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
