Bazaar focus for 2.1 and 2.2
James Westby
jw+debian at jameswestby.net
Wed Dec 16 23:29:55 GMT 2009
On Wed Dec 16 23:09:28 +0000 2009 Martin Pool wrote:
> To me this meant: per-file merge hooks, making merge-package fit
> better with bzr merge, ... There may not be enough here that it's an
> actual theme in its own right distinct from 'udd bugs'.
I would welcome any help in making merge-package go away. I posted about
its raison-d'être, so that would be the main target if someone wanted
to do that.
> >> So I think overall:
> >>
> >> for 2.1 (about four working weeks before rc1 and going to
> >> safe-bugfix-only mode):
> >> * bugs coming from: merging unrelated branches in recipes, pkg and
> >> vcs import failure bugs, other udd bugs (including specific merge
> >> scenarios)
> >> * filling those bug queues
> >
> > I think this is good.
>
> > I can fill the queues with package import failure bugs, and encourage
> > my fellow developers to report anything they hit. Who will fill
> > them with vcs-import failure bugs. Do we have an analysis of which
> > issues are causing the most failures? Also, looking at the few that
> > fail for the top 100 would be good (and perhaps setting up imports
> > for more of that 100.)
>
> There was a thread on launchpad-dev (I think) with some analysis of
> the failures, and we can dig into that more.
Great. I couldn't find anything in my archives with a quick search.
The mails I found suggested that the information is not readily available
in a combined form. (You can go to any import to see why it failed, but
getting the list of failures with reasons is harder).
Thanks,
James
More information about the ubuntu-distributed-devel
mailing list