From Wikipedia, the free encyclopedia Roundup (issue tracker)
Roundup (issue tracker)
Roundup (issue tracker) Database schema
Developer(s) Richard Jones
The database schema is defined in a Python file in the
Initial release August 18, 2001 (2001-08-18) tracker instance’s root directory; it is re-read whenever
the server is started anew. When changes are found (e.g.
Stable release 1.4.17 / May 13, 2011 (2011-05-13)
new attributes), the tables of the underlying RDBS are al-
Written in Python tered accordingly.
Operating system Cross-platform
Page templates
Type Issue tracking system
Roundup uses the Template Attribute Language (TAL)
License Modified BSD license[1] known from Zope to create HTML or XHTML output.
Some templates are used for several classes, e.g. _gener-
Website roundup-tracker.org
ic.index.html, which allows (authorized) users to change
Roundup is an open-source issue or bug tracking system the objects of all classes which lack an own index tem-
featuring a command-line, web and e-mail interface. It is plate.
written in Python and designed to be highly customiz- When an "issue123" is requested, this designator is
able[2]. Roundup was designed by Ka-Ping Yee for the split in the issue class and the id "123"[9]. By default an
Software Carpentry project and has been developed since "item" template is chosen: First, an issue.item.html tem-
2001 under the direction of Richard Jones. It is currently plate file is looked for; if it can’t be found, _gener-
the issue tracker for the Python programming language ic.item.html is used as a fallback option. If this is missing
itself[3]. It was once described as "like Bugzilla without equally, an error occurs.
the six years of training, or RT without that tedious
MySQL rubbish."[4] Detectors
Many Roundup functions, including some of the standard
functionality, are implemented using so-called detec-
Features tors[10], which are located in the "detectors" sub-directo-
The standard configuration of Roundup features: ry of the tracker instance. They are Python subroutines
• a web interface for viewing, editing and searching which have access to the object to change (if already cre-
issues ated) and the requested attribute changes.
• a Mail gateway allowing creation and changing of Detectors are distinguished between auditors and re-
issues[5] actors. Auditors are used primarily for several automatic
• a database abstraction layer, currently supporting changes (in the standard configuration, the assignedto
(among others) Python’s built-in "anydbm" module, user is automagically added to the nosy list of the issue),
PostgreSQL, MySQL and SQLite and to refuse un-allowed changes; reactors are executed
• issue-specific "nosy lists", used for e-mail thereafter and used e.g. for the e-mail notification fea-
notifications and conversation (each issue effectively ture, sending notification mails to all users interested in
becoming a mini mailing list) [6] a certain issue when a comment is added to it.
• an authorization system[7], based on roles (of users), Detectors are triggered whenever one of the actions
classes and objects • create
• an interactive shell for backup and restore tasks and • set (change of attributes)
for manipulation of objects • retire
Roundup runs as a daemon process, CGI script[8] or alter- • restore
natively using WSGI (mod_python is supported but that is requested. They can be used to create an elaborated
project is no longer in development). custom workflow.
Concepts Extensions
The instance subdirectory "extensions" can hold addi-
Roundup is customized by changing the contents of the tional files which are needed for extended functionalities
tracker instance directory:
1
From Wikipedia, the free encyclopedia Roundup (issue tracker)
which can’t (conveniently) be done with TAL; even total- [3] TrackerDocs - PythonInfo Wiki
ly new actions are possible. [4] NTKnow 2002/07/05 - TRACKING
Python modules which are used by both detectors [5] E-Mail User Interface, Roundup design description
and extensions can be put in the "lib" subdirectory [6] Design of Nosy Lists
[7] access control, Roundup design description
See also [8] usage via CGI is rare and not recommended, for
performance reasons
• Comparison of ticket-tracking systems [9] identifiers and designators, Roundup design
description
References [10] detector interface, Roundup design description
[1] Roundup licensing
[2] The primary user interface is the web interface. A External links
so-called classic tracker template is distributed • Project site at sourceforge
as the standard template and data structure set, • Ka-Ping Yee’s Design proposal
but can be used as a starting point for • Ka-Ping Yee’s Implementation guide
customization • Roundup Issue Tracker - PyCon 2005 Presentation
Retrieved from "http://en.wikipedia.org/wiki/Roundup_(issue_tracker)"
Categories: Bug and issue tracking software, Free project management software, Free software programmed in Python,
Web applications
This page was last modified on 14 June 2011 at 18:25. Text is available under the Creative Commons Attribution-
ShareAlike License; additional terms may apply. See Terms of use for details. Wikipedia® is a registered trademark of
the Wikimedia Foundation, Inc., a non-profit organization.Contact us
Privacy policy About Wikipedia Disclaimers Mobile view
2