很多项目之所以成功，就是总经理亲自带队全程参加整体CRP测试，整整在会议室坐了一个半天。我们说ERP工程是“一把手工程”，如果说一把手的确做到全程参加整体CRP的话，从这一点看那一把手工程就是落到了实处。当然我们的CRP测试必须是用企业真实的数据、真实的流程，得出真实的结果，而不是瞎编几个数据，走个形式。CRP测试的理念必须是以业务流程为主线来测试，测试流程和数据，而不是仅仅测试系统有没有问题。

What is it?  它是什么？

Mantis is a web-based bugtracking system. It is written in the PHP scripting language and

requires the MySQL database and a webserver. Mantis has been installed on Windows, MacOS,

OS/2, and a variety of Unix operating systems. Almost any web browser should be able to

function as a client. It is released under the terms of the GNU General Public License

(GPL).
Nantis 是一个基于web bug追踪系统。它使用php脚本语言和需要Mysql 数据库和一个web服务器。Mantis

已经被安装在Windows、MacOS、OS/2和各种各样Unix操作系统中。几乎所有的web浏览器应该可以做为一

个客户端功能。它被在GNU通用公共license(GNU)下发布。

Mantis is free to use and modify. It is free to redistribute as long as you abide by the
distribution terms of the GPL.

Mantis是免费使用和修改的。它是在GPL原则下可以被重新修改分配的。

History 历史

Mantis started as an internal bug tracking tool for a pet project (video game). Good, free

packages were lacking at the time so a bugtracker was written. Since then, Mantis has been

totally re-written and make it available to the public.

Mantis开始作为一个为pet项目（视频游戏）的内部bug追踪工具。免费的包缺少在时间，所以bug追踪被

写出。从那以后，mantis被重新编写并且将它公布与众。

Goals 目标

The goals for this project are to produce and maintain a lightweight and simple bugtracking

system. Additions of complexity and/or features are modular and configurable so that users

can be shielded from unwanted clutter.

这个项目的目标是产生和维护一个高亮度并且简单的bug追踪系统。复杂的附加特征被模块化并且被注册

这样，用户可以避免不想要的混乱。

The product is designed to be easily modifiable, customizable, and upgradeable. Anyone with

intermediate PHP and MySQL experience should be able to customize Mantis to suit their

needs.

这个产品被设计成很容易修改，可定制、和可升级的。伴随Php和MySQL经验的任何人应该可以定制Mantis

来满足他们的需要。

Features and Benefits 特性和用处

Free  免费
Easy installation  容易安装
Web based   基于web
Platform independent  平台独立
Multiple projects   多项目
Multiple languages  多语言
Emailing     邮件
Simple Search  简单搜索
Viewing filters   过滤显示
PHP    php

Upcoming Features 将来的特征

Check the Roadmap for a more detailed and sometimes up to date list of items.

Versioning

The release numbering convention used is major.minor.micro (eg. 0.18.2).

Major - Indicates a very large change in the core package. Rewrites or major milestones.
Minor - Significant amount of feature addition/modification.
Micro - Usually bug fixes or minor features
How to Help

Report real bugs to the Development Bugtracker
Suggest (reasonable) features
Contribute code or tell us where to look.
Let us know if you find it useful. We won't publish the information without permission, but

we appreciate the feedback!