GitHub issues

[Ian Booth]

We discussed this topic at the team meeting and Launchpad will remain the
primary issue tracker. We'll leave Github's issue tracker enabled for a bit and
see how many bugs are raised. Any legitimate bugs will need to be copied across
to Launchpad. Launchpad can import bugs on other trackers for sure, but them we
can't use it standalone. If the volume of bugs raised on Githb becomes a flood,
we'll have to look at other ways of automating the import into Launchpad and
dealing with the associated workflow and sync issues.

On 05/06/14 16:29, Gustavo Niemeyer wrote:
> The comment was made with the understanding that this was your original
> plan, and the point is to measure engagement before closing it down, or
> you'll never know whether it makes any difference for juju specifically.
> Also,  isn't Launchpad able to track issues originally filed on other
> trackers? That used to be one of its big selling points for distro work.
> 
> gustavo @ http://niemeyer.net
> On Jun 4, 2014 10:43 PM, "Ian Booth" <ian.booth at canonical.com> wrote:
> 
>> Actually the original plan was not to enable Github's issue tracker and
>> continue
>> using Launchpad's. Having 2 issue trackers is not optimal and will create
>> too
>> much management overhead and wasted effort. We are continuing to use
>> Launchpad's
>> milestones for scoping and planning releases etc and of course this all
>> ties in
>> with Launchpad's issue tracker.
>>
>> So I'd prefer to stick with the plan and disable Githubs's tracker. This
>> was
>> meant to be done when the repo was set up.
>>
>> On 05/06/14 00:23, Gustavo Niemeyer 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.
>>>
>>> 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
>>>
>>>
>>>
>>
>