ability to link to a bug for failing code imports

[Jelmer Vernooij]

It would be nice if it was possible to link failing code imports to the bug in the foreign vcs plugin bug / bzr bug / cscvs bug.

Having this allows:

* Users to follow the progress on the bug that's causing the failure of their import
* Easier to re-enable all imports that were affected by a particular bug
* Easier to find failing imports because of unknown/unreported bugs or invalid imports

[Tim Penhey (thumper)]

This could almost be seen as an extension of the bug dependency idea.

Instead of saying that this bug is dependent on that bug, we *could* say, this
_entity_ is blocked on this bug.

  importance low
  status triaged
  affects malone

[Jelmer Vernooij (jelmer)]

On Fri, 2010-08-20 at 00:45 +0000, Jelmer Vernooij wrote:
> ** Branch linked: lp:~jelmer/launchpad/code-import-bug-link
The attached branch adds a database field for a related bug id to
CodeImport. Is this a reasonable approach?

Is there anybody in particular I can ask for pre-implementation calls
for branches related to code imports?

Cheers,

Jelmer

[Tim Penhey (thumper)]

On Wed, 25 Aug 2010 11:17:39 you wrote:
> On Fri, 2010-08-20 at 00:45 +0000, Jelmer Vernooij wrote:
> > ** Branch linked: lp:~jelmer/launchpad/code-import-bug-link
>
> The attached branch adds a database field for a related bug id to
> CodeImport. Is this a reasonable approach?
>
> Is there anybody in particular I can ask for pre-implementation calls
> for branches related to code imports?

Yes, me :-)

[Jelmer Vernooij (jelmer)]

On Wed, 2010-08-25 at 01:23 +0000, Tim Penhey wrote:
> On Wed, 25 Aug 2010 11:17:39 you wrote:
> > On Fri, 2010-08-20 at 00:45 +0000, Jelmer Vernooij wrote:
> > > ** Branch linked: lp:~jelmer/launchpad/code-import-bug-link
> >
> > The attached branch adds a database field for a related bug id to
> > CodeImport. Is this a reasonable approach?
> >
> > Is there anybody in particular I can ask for pre-implementation calls
> > for branches related to code imports?
>
> Yes, me :-)
Great! Could we have a pre-implementation call about this sometime?

Cheers,

Jelmer

[Jelmer Vernooij (jelmer)]

On Tue, 2010-08-31 at 01:39 +0200, Jelmer Vernooij wrote:
> On Wed, 2010-08-25 at 01:23 +0000, Tim Penhey wrote:
> > On Wed, 25 Aug 2010 11:17:39 you wrote:
> > > On Fri, 2010-08-20 at 00:45 +0000, Jelmer Vernooij wrote:
> > > > ** Branch linked: lp:~jelmer/launchpad/code-import-bug-link
> > >
> > > The attached branch adds a database field for a related bug id to
> > > CodeImport. Is this a reasonable approach?
> > >
> > > Is there anybody in particular I can ask for pre-implementation calls
> > > for branches related to code imports?
> >
> > Yes, me :-)
> Great! Could we have a pre-implementation call about this sometime?
More specifically, do you think my initial approach of adding a separate
database field for linking bugs onto code imports is the right one?

Cheers,

Jelmer

[Tim Penhey (thumper)]

On Tue, 31 Aug 2010 11:48:46 you wrote:
> On Tue, 2010-08-31 at 01:39 +0200, Jelmer Vernooij wrote:
> > On Wed, 2010-08-25 at 01:23 +0000, Tim Penhey wrote:
> > > On Wed, 25 Aug 2010 11:17:39 you wrote:
> > > > On Fri, 2010-08-20 at 00:45 +0000, Jelmer Vernooij wrote:
> > > > > ** Branch linked: lp:~jelmer/launchpad/code-import-bug-link
> > > >
> > > > The attached branch adds a database field for a related bug id to
> > > > CodeImport. Is this a reasonable approach?
> > > >
> > > > Is there anybody in particular I can ask for pre-implementation calls
> > > > for branches related to code imports?
> > >
> > > Yes, me :-)
> >
> > Great! Could we have a pre-implementation call about this sometime?
>
> More specifically, do you think my initial approach of adding a separate
> database field for linking bugs onto code imports is the right one?
>
> Cheers,
>
> Jelmer

I'm not entirely sure. One possibility is to put a type on the bug-branch
link. So we could have things like "fixes", "blocked by", "causes"...

Maybe that is just crazy thought.