After some chatting, we have decided on a move to Roundup for our
tracker. The big reasons for this choice are the offer of help from
the CPython community, and Raghuram Devarakonda's kind offer to for
volunteer for support. Next steps will be for us to figure out the
the way we want our current tracker's data to be mapped to a new
roundup instance.
Below I have a request from Martin v. Löwis on the Python-Trakcer list:
As a further follow-up, I also need a list of components (the things
where the Python tracker has "Build", "Distutils" etc), and any mapping
between SF categories and roundup components - take particular notice
that all three SF trackers will be merged into a single one.
The same is also needed for priorities: the existing config maps
1..4 to low, 5 to normal, 6 and 7 to high, 8 to immediate, and 9
to urgent. I see that the Jython tracker has nothing above 5, but
also has 4, 3, 2.
Also, the SF "Group" maps to the Roundup "Version"; I need a list
of mappings here, as well.
Then, we need a list of issue_types; the Python tracker has
crash, compile error, resource usage, security, behaviour, rfe;
it's not clear whether this aspect is even useful, though.
The resolutions will map 1:1 unless you want customization there,
as well.
It would best to specify all this on either a Wiki page somewhere,
or in a meta-tracker issue, at
http://psf.upfronthosting.co.za/roundup/meta/
Regards,
Martin
|