Opened 14 years ago
Closed 13 years ago
#1 closed defect (fixed)
OpenMCL hasn't really had a bug-tracking system in years
| Reported by: | gb | Owned by: | gb |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | project hosting | Version: | unspecific |
| Keywords: | bug-tracking | Cc: |
Description
The bug-openmcl mailing list sort of works, but is less than ideal.
Hopefully, using Trac to manage bugs will be better.
TBD: what kinds of email integration are possible and desirable ?
Change History (4)
comment:1 Changed 14 years ago by gb
- Version changed from 1.1 to unspecific
comment:2 Changed 13 years ago by bfulgham
The MacPorts? project has an e-mail integration such that newly applied commits to svn cause e-mail to be sent to subscribed users (examples: "http://lists.macosforge.org/pipermail/macports-changes/2006-September/thread.html")
Will Trac also be used as the main "Wiki" for OpenMCL? I'd like to dump some information that I've found helpful into the system somewhere...
comment:3 Changed 13 years ago by gb
Commits to the svn trunk get propagated to CVS.
Commits to the the bleeding-edge CVS tree trigger mail to the list "openmcl-cvs-notifications@…".
Somewhere down the line, CVS might get phased out (at which point having email-on-svn-commit would make more sense.)
I'd sort of like to phase the old wiki out; Trac offers the ability to link to the bug database and svn history from its wiki, and there seems to be an active community developing extensions for it. Let's see how it goes; if it seems featureful enough as a wiki, we can migrate content from the old wiki here. If it seems too limited, I'll look into installing something else. (Selfishly, I'd like to try to use Trac, since it means one thing to maintain/configure rather than a few things.)
comment:4 Changed 13 years ago by gb
- Resolution set to fixed
- Status changed from new to closed
Trac is a bug tracking system.
Set version to "unspecific", to see what happens ...