Changes

Jump to: navigation, search

Bug Tracker for Pidora

323 bytes added, 21:53, 9 October 2013
Project Plan
=== Tracking ===
Trac While there isn't much version control needed, I may use github to track Trac? =)keep changes to configuration files as I work on them.
<!-- Describe the tracking mechanisms you are using for your project (bugzilla, trac, github, ...) -->
<!-- Note: Each student must have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. -->
* 0.1
**Research Decide between BugZilla(currently the leader), and test each of the Trac.**Install chosen application and any necessary spam filtering modules that look promisingon a local machine/drive.**Test installation against spam (possibly use cases already in Pidora bug tracker).
* 0.2
**Implement the application (and modules that show significant decrease in spam) on Production environment.
* 0.3
**???ProfitMake any necessary changes to enhance performance. 
== Communication ==
1
edit

Navigation menu