Bug tracker import code (moved): Difference between revisions

Content added Content deleted

Inline

Latest revision as of 18:44, 22 August 2012

This is a page about improving or modifying OpenHatch.

We call that "Hacking OpenHatch," and there is a whole category of pages about that.

We are updating our documentation system. This page is now included in our project package, and is automatically generated by sphinx at openhatch.readthedocs.org Bug tracker import code

@@ Line 1: / Line 1: @@
+{{Hacking OpenHatch}}
-Here's what you need to know:
+We are updating our documentation system. This page is now included in our project package, and is automatically generated by sphinx at openhatch.readthedocs.org [http://openhatch.readthedocs.org/en/latest/internals/index.html#bug-tracker-import-code Bug tracker import code]
-* Each ''style'' (like "Bugzilla", "Roundup", and so forth) of bug tracker has its code in mysite/customs/bugtrackers/''{{style}}''.py.
-* We write tests in mysite/customs/tests.py for each bug tracker type.
-The Roundup code is instructive. Look at that in your favorite editor. You'll see:
-* class RoundupTracker
-** This class's __init__() is built so that an instance has enough data that a call to grab() will start downloading bug data.
-The rest of that file is trivial subclasses that pre-fill the data to __init__(). That way, they can be called once a day by the mysite/customs/management/commands/customs_daily_tasks.py .
-So if you want to add a new Roundup-based bug tracker, add a new subclass to that file, and submit a patch.
-(Wondering how to submit a patch? Read [[how we handle patches]].)
-[[Category:Hacking OpenHatch]]