Re: [Jython-dev] What would everyone think about moving Jython's bug tracking to CPython's tracker?

[<fwi...@gm...>]

On Sat, Feb 16, 2013 at 10:39 AM, Jeff Allen <ja...py...@fa...> wrote:
> I kept quiet for a while as I have little understanding of what is under the
> covers of the trackers. I had assumed the Jython tracker was just the same
> software as the Python one, with obvious configuration differences, and had
> simply not kept up. The two repo histories seem to confirm this. With my
> limited understanding, I'd have gone for the route you're taking for now.
>
> My first thought was that it would be needlessly confusing and probably a
> bit unwelcome to the CPython team. People would want filtered views, and
> those who study bug fix rates and backlogs would surely want separate scores
> and summaries. Apart from the fact that the issue numbers form a single
> sequence (which would help in certain contexts), that almost sounds like two
> interfaces, albeit off a single infrastructure back stage. It sounds like it
> would work technically.  I think the business case would be that the work
> involved in the interface development and renumbering everything exceeded
> the maintenance of keeping the two in sync  ( ... hinges on whether it does,
> I mean). And the "human case" is more to do with comfort amongst, and
> togetherness with, the CPython community.
>
> Support for Rietveld, as identified by Alan, looks like it would be useful
> if we took a more sophisticated approach to review. I don't see why that
> requires a single tracker as opposed to reproducing what CPython have done.
I've come to the same conclusions. I had worried that adding the
features of the CPython tracker would be too much work, but now that
i've had a better look it seems to me that upgrading our tracker will
not be that bad and will turn out to be the better path.

-Frank