Hi there,
On 15.09.2012 08:04, Russel Winder wrote:
On Fri, 2012-09-14 at 09:22 -0400, Gary Oberbrunner wrote:
[…]
Nobody really likes the Tigris tracker. There was some work to start
migrating away from it a while ago (Anatoly I think?), but I think we
decided to get the code over to bitbucket first, and then worry about
the tracker.
Maybe that time has come?
I don't think the Tigris tracker is that bad. I could live with it for
another while. ;)
So where to go? The obvious place is the BitBucket issue tracker that
can be associated with the SCons mainline. But I had the feeling that
people thought it even worse than Tigris for various reasons. On the
other hand it would integrate with the pull requests and the repository.
Whether we switch to something else, and to which tool, depends on what
we want our workflows to be. In the past we had rather strict rules
regarding the bug triaging and setting of milestones. And in my view, a
user that enters a bug still shouldn't care about whom to assign it to.
It's the task of the SCons team to negotiate who cares about the issue,
or the single developer if he simply "grabs it".
I haven't looked at the Bitbucket tracker in a while. But back then it
wasn't possible to set milestones, and priorities were grouped into
something like "easy", "middle" and "hard".
Could we live with this?
I guess the real question is what is the toolchain for getting all the
material out of Tigris and into<wherever>. I would have guessed that
there should be an XML or JSON dump of the Tigris database possible.
I wrote some Python classes that are able to extract data from the
issues database and write them into an XML format. The other problem is
now to get this data "into" the new tracker on the other end.
How would you accomplish this with the Bitbucket tracker?
Best regards,
Dirk
_______________________________________________
Scons-dev mailing list
[email protected]
http://two.pairlist.net/mailman/listinfo/scons-dev
