GitHub issues

[Andrew Wilkins]

On Wed, Jun 4, 2014 at 10:23 PM, Gustavo Niemeyer <gustavo at niemeyer.net>
wrote:

> I would keep them around for a while and try to observe how the
> community reacts to the availability. If people don't care, then just
> closing it sounds fine. If you start to get engagement there, might be
> worth going over the trouble of supporting users that live in that
> ecosystem. My experience has been that I got significantly more
> engagement, including bugs, once moving over projects to github.


Sounds sensible. I'll look into updating the lander to link to the commit
in a linked LP bug, and let's leave the GitHub Issues around for now.

On Wed, Jun 4, 2014 at 10:13 AM, Curtis Hovey-Canonical
> <curtis at canonical.com> wrote:
> > On Wed, Jun 4, 2014 at 6:36 AM, Andrew Wilkins
> > <andrew.wilkins at canonical.com> wrote:
> >
> >> What are our options? Is it simplest just to disable GitHub issues, and
> have
> >> the lander pick up "fixes lp:NNNNNN" and add a comment to the bug in
> >> Launchpad?
> >
> > I think this is the easiest path.
> >
> >
> >
> > --
> > Curtis Hovey
> > Canonical Cloud Development and Operations
> > http://launchpad.net/~sinzui
> >
> > --
> > Juju-dev mailing list
> > Juju-dev at lists.ubuntu.com
> > Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>
>
> --
>
> gustavo @ http://niemeyer.net
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140605/e1a43ab1/attachment.html>