Instructions on how to use TRAC on CentOS

Installation of SVN

First step: Install the SVN client software first, then click the arrow icon

Second step: appear as shown in the page, enter the SVN URL svn://192.168.1.197/opt/trac-1.0.1-3/apps/trac/trac_repositories/repository/Click OK,

SVN file creation, import, export

Appears as shown in the page, right-click in the right margin, appears as shown, Arrow 1 refers to the Add file, Arrow 2 refers to the Add folder, Arrow 3 guides out some files.

File import, right-click within the folder to select Tortoisesvn->import,

After the show appears, click OK, enter the user name, password can be uploaded, after uploading in the Web site can be seen in the source browser to upload files. As shown below

Use of TRAC

Enter the server IP in the URL input box of any browser (here I temporarily use the intranet 192.168.1.197 IP as the server), enter after entering will see the icon as shown below, click Access Bitnami Trac stack to enter,

After entering the main page, click Login in the upper right corner to enter your username, password

Then it goes to the TRAC main page. As shown

Introduction and use of TRAC functions

There are some wizards in the upper right-hand corner of this figure, and we will give you a general explanation of their respective roles.

Personal settings, help/Guides

Name implies. Here is not much nonsense, everyone look good.

Time Line

Here's the timeline, according to the page everyone should be able to guess its use, good, here is based on the time for the record point, provides a history of the project in a single report. It lists all trace events that occur chronologically, a brief description of each event, and, if applicable, the owner's change.

These types of events are listed in the time table:

Wiki Page event creation and change

Ticket activity creation and resolution/close (and other optional changes)

Change the check of the source code base

Milestone Milestones Completed

Each event item provides a link to the specific issue of the event, he writes the changes as well as a brief excerpt of the actual comment or text.

Create a task order, view a task order, a roadmap (milestone)

Roadmap provides ticketing system to help plan and manage the future development of the project views

Basically, this roadmap is just a series of future milestones. You can add a description of the milestones (using wikiformatting) that describe the main goals, for example. In addition, for a milestone ticket aggregation, the ratio between active resolution tickets is shown as a milestone progress bar. It is possible to further customize the ticket groupings and show the progress bar with multiple tickets on the status.

The roadmap can filter to show or hide completion milestones, milestones, and no due dates. In this scenario, the completed milestone and hidden milestone date are displayed without a selected milestone date that is not completed.

About the life cycle of the TRAC Management software project:

To manage a project with TRAC, it is necessary to do the following work:

Dividing milestones

Division of items

Dividing ticket

Master the operation mechanism of ticket

Master the view and use of change history

Proficiency in milestone viewing and use

The first three items belong to the project structure, and the latter three belong to the scope of operation. For the preceding three individual partitioning principles are:

Dividing milestone principles:

Milestones are events that we set up to show that when these events occur, our work has reached a certain level. As for the choice of events as a milestone, it is in fact the choice of project stakeholders most concerned about the event as a milestone. The event or point of time is the best milestone, and the milestone is able to mark the project's progress because it is a matter of concern to the project's stakeholders, and the meaning of the milestone marking progress is also the meaning of the event.

Divide the component principle:

In general, according to functional modules, such as collaborative Office system can be divided into document processing, personal office, e-mail and so on.  The relationship between components and milestones is that a component can belong to multiple milestones, and of course a milestone can contain multiple components, which are many-to-many relationships, but are milestone-oriented in Trac, so we should stand on the milestone axis to manage the software project. The specific component how to divide, this need to be decided with the actual situation.

Divide the ticket principle:

Any problems during the development of the project can be identified with a ticket, such as bug, Project plan, function improvement, project proposal, Todo and so on, can be written as a ticket, the developer through the access to view the ticket system, can timely understand the project progress, The place to be solved, etc.
Each ticket can be modified and explained (Description property), and whether the ticket is a bug or a project proposal or something (type attribute), which person is responsible for this ticket (Assigned To/owner property), Set the priority of the ticket (first attribute), set the final finish time of the ticket (milestone property), and set which module this ticket belongs to (component attribute). A milestone contains a name and time, where time is the expected end time of this phase of the project, and we set this property to indicate which milestone the ticket is to be created, which stage of the project, and at what time.

The display, then, is a detailed illustration of the production of a task item:

1. Represent an outline or an indication of a project.

2. Who initiated the task on behalf of this project.

3. Represent the key overview or project requirements for this project.

4, represents the type of this project, is defect defect, enhancement strengthening, task tasks. You can indicate what type of task is here when you are laying out a task.

5, is a milestone, can be customized according to the project name, you can clearly list all the milestones of the project.

6, is version control, can be based on different versions to choose.

7, is cc, copy to others, with a comma separated by a mailing list, you can talk about the change notice to all the people involved.

8, is the priority, the default is low, medium, high, emergency, major five levels, according to the urgency of the task to choose.

9, is a component, can be divided into functional modules, such as collaborative Office system can be divided into document processing, personal office, e-mail and so on.

10, keywords.

11, belong to the main, if this is to a person's task, then you can directly enter the name of the principal.

12, is the accessory, can insert the attachment according to the need.

·

Ticket operation status switch diagram such as
Under

650) this.width=650; "Name=" image_operate_93821414310071660 "src=" http://s4.sinaimg.cn/mw690/ 005b486dzy6n7fp7dfd03&690 "width=" 407 "height=" 385 "alt=" on CentOS on the use of TRAC "title=" instructions on the use of TRAC "style=" on CentOS Margin:0px;padding:0px;border:0px;list-style:none; "/>

The state diagram clearly shows a ticket operating life cycle in a TRAC instance.

When a member gets a ticket, the following actions can be done:

Select the modified word as shown here, just to modify its zodiac

650) this.width=650; "Name=" image_operate_87831414310103349 "src=" http://s6.sinaimg.cn/mw690/ 005b486dzy6n7fqxambe5&690 "width=" 690 "height=" 336 "alt=" on CentOS on the use of TRAC "title=" instructions on the use of TRAC "style=" on CentOS Margin:0px;padding:0px;border:0px;list-style:none; "/>

1, Leave as new does not change, refers to the ticket action, used to modify only ticket properties and reply ticket when used. Note that the content of this item will change depending on the state of the ticket.

2, Resolve to: Close this ticket need to choose the reason, including repair, invalid, custom repair, repeat, my work

3. Reassign to reassign to

4, accept their own receiving, and processing (get the task if correct, first accept)

SOURCE Browse

The TRAC library browser can browse specific versions of directories and files stored in the Knowledge base associated with the TRAC environment.

The top level of the repository browser is the index library, which lists all the configuration libraries. Each library has a name as a "virtual" file hierarchy that includes the path prefixes for all available repositories. A library can be configured with a doff thy name, which is the default library. When such a default library is present, top-level files and directories are also listed in the default library segment placed in the index library. If the default library has a unique knowledge base that is slightly related to the TRAC Environment Library index

Catalog entries are displayed in a list of sortable columns. The entries in the list can be based on the name, size, age, and author by clicking on the column headings. The sort order can be reversed by clicking on a given column header.

The browser can browse the directory structure by clicking on the directory name. Clicking on the filename displays the contents of the file. Clicking on the version number of a file or directory will take you to the tracrevisionlog of the file. Note that there is also a navigation link to modify the log, and the current path is checked to do the same thing. Clicking on a different icon after the modified number will show the file and modify the changes. Click on file-age will take your timesheet, change set

Browsing directories or files, they have historically also been possible, in any given library version. The default behavior is to display the latest revision of another version number to make it easy to modify the selection of input fields using the view at the top of the page.

Management

650) this.width=650; "Name=" image_operate_32251414310154708 "src=" http://s6.sinaimg.cn/mw690/ 005b486dzy6n7fviq21a5&690 "width=" 690 "height=" 296 "alt=" on CentOS on the use of TRAC "title=" instructions on the use of TRAC "style=" on CentOS Margin:0px;padding:0px;border:0px;list-style:none; "/>

Management is to make some simple settings as an administrator.

TRAC permissions are divided into 7 categories: Warehouse Browser, subpoena system, Roadmap (Roadmap), report, wiki system, Rights Management (Admin), others. The list is as follows:

For more information, please inquire qq:1183810577

This article is from "You 70 years" blog, please be sure to keep this source http://chavaz.blog.51cto.com/6876806/1850792

Instructions on how to use TRAC on CentOS