This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
Hi all -
We've finally got a bug tracker running again. Since RT had some
problems that we couldn't figure out how to work around (namely,
sending tons and tons of e-mail when ticket status changed) and it's
interface made it difficult to generate custom queries, we decided to
look for other options. After some searching, it seemed that a
project called Trac would give us what we were looking for, and has
some nice integration with Subversion.
The new URL for our bug tracker is:
By default, you will see the anonymous view, which basically allows
you to do nothing more than see the open bugs in the system. If you
click on the "login" button and use your SVN username / password, you
will be able to file bugs and see more information about the current
state of the SVN repository. As we discussed, only developers with
SVN access can create or modify bugs. In the future, this may
change, of course.
Using the system is pretty self explanatory. One thing I should
point out is that a "milestone" is an upcoming release for which the
bug must be fixed / implemented / etc. A "version" on the other
hand, is where the bug was discovered.
By default, the only people who are some how participating in the bug
(either by creating it, being assigned the bug, or have added
themselves to the cc list) will receive e-mail notification on
change. If you want to receive an e-mail whenever any bug in the
system changes, you can re-subscribe to the bugs_at_open-mpi mailing list.
There are some nice reports that you can view to get information on
current bugs. These include:
- tickets without owners
- "my" open tickets
- tickets for each milestone
It's quite easy to add new reports, so if you have ideas on what you
would like to see, please let me know. Jeff has already suggested a
milestone view that only shows bug reports (as opposed to bug reports
+ feature requests). I'll probably add that in the next day or two.
Right now, we're still playing around with the integration between
Trac and Subversion. But it should be possible to change the status
of a ticket from a SVN commit message. It's also possible to
associate a commit with a particular bug number by adding something
like "ticket:1" (without the quotes) to your commit message to
associate the commit with ticket # 1. The ticket will automatically
be updated to reflect the connection.
I'll add bugs as they come in on the users and devel mailing lists.
I'll also be hounding people to pick up unassigned bugs. For now,
plan on receiving e-mails about unassigned bugs on Mondays and then
hearing about them on the weekly telecon ;). Please let me know if
you have any questions about the bug tracker.
Open MPI developer