Recently, I have been searching for a bug tracking system that best suits me. I usually write some gadgets, and some bugs need to be tracked and managed. The format of notepad is too casual and difficult to manage.
I tried many well-known tools, such as Bugzilla and mantis, and it felt too heavy. It was quite suitable for the team.
Later, I thought about defining a log database in XML, opening a file with a bug, so that I could record the bug content, solution process, and methods in detail. Write a front-end to manage and organize these XML files. However, I have a small number of bugs. More often, I just need to write some ideas. This rigorous XML organization method does not make me feel more relaxed.
I tried to use Emacs muse to record a period of time. One drawback is that many of the solutions I wrote down are: Code If I do not add the <verse> </verse> label, muse will try to help me escape it again. In general, Muse is a little more typographical, and is not suitable for recording what you want to write at will.
Finally, I found that using the Perl pod to do my own bug tracking system is quite good. Although the pod is a document system, as long as labels are used flexibly, it can also be used as a simple bug tracking system. The advantage of pods is that when you do not need to use commands, you can directly enter your content. In general, it is relatively simple.
The pod format is defined as follows:
= Pod
= Head1 project 1
= Head2 bug #000001
= Head3 bug # A brief description or title of 000001
Bug #000001 details, all related content ..
= Head3 bug status: fixed
= Head3 bug solution record
= Over indentlevel
= Item solution Step 1
Solution 1.
= Item solution Step 2
Solution 2.
= Item bug fix Summary
Solution of bug #000001, the summary of this bug is:
Try to readcord the document in time and in style.
Here is a summary of the bug.
= Back
= Head2 bug #000002
= Head3 bug # A brief description or title of 000002
Bug #000002 details, all related content ..
= Head3 bug status: Active
= Head3 bug solution record
= Over indentlevel
= Item solution Step 1
Solution 1.
= Item solution Step 2
Solution 2.
= Item bug fix Summary
Solution of bug #000002, the summary [...]
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.
