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.

Jeff Allen

On 14/02/2013 16:59, fwierzbicki@gmail.com wrote:
On Wed, Feb 13, 2013 at 11:17 PM, Alan Kennedy <jython-dev@xhaus.com> wrote:
Would it really be that difficult to migrate the contents of our roundup
database to theirs?
Well, what I don't want to do is drop 300+ inconsistently
addressed/maintained bugs on the CPython community.... but I see  your
point about the undesirability of a split tracker and the value of our

So regardless of whether we migrate or not, the first order of
business is to get our tracker straightened out. I think I'll give
upgrading our current tracker a harder look. Maybe we can get our own
tracker to look as nice as CPython's....

So I'm going to switch gears and look at what it takes to upgrade us.
If anyone has time to look into this instead of me, let me know - I'd
prefer to do other stuff, but I think this is too important to let rot
anymore. To get an idea of what it would take see this doc:


The Jython tracker is mentioned at the bottom of the doc - mainly you do

hg clone http://hg.python.org/tracker/jython/

Instead of

hg clone http://hg.python.org/tracker/roundup

for one of the steps.


Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
Jython-dev mailing list