Bug Tracking System Vs SVN/CVS. Presented by Sneha Mudumba. Bug tracking system.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
tracking system is a database that
records facts about known bugs.
control system that keeps track
of all changes in a set of files,
typically the implementation
of a software project and it
allows several developers to
The major components in CVS is a repository which is master copy where CVS stores a full revision history.Concurrent version system
Repository:The master copy
where CVs stores the revision
Working Copy:The copy in
which actual changes are made.
Typical CVS system supports
several programmers to work
concurrently.The server will accept
the changes made to the most
recent version of file.Developers
are therefore expected to keep
their working copy up to date by
incorporating other peoples changes.
Limitations of CVS1. CVS only shows what the conflicts are but does not give a procedure to solve it 2. Limited support for Unicode text file and non -ASCII filenames.
Mantis and TRAC:Mantis is an example of web based bug tracking
system.It is written in PHP and requires a SQL database Server.It is a lightweight ,simple bug tracking system.
TRAC matches to mantis.
So the Bug tracking system and the Concurrent version system both enable the programmers to keep track of the bugs by using different mechanisms and there by enable the programmers to resolve the errors in a easy way