Trac: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
 
(9 intermediate revisions by 7 users not shown)
Line 1: Line 1:
'''Trac''' is an online system for tracking software bugs and organizing software development. OLPC uses trac to coordinate all its official software development. Bugs, features, and other work items are entered into trac as '''trac tickets'''. This assigns the work a unique reference number, which can be used to track progress using the trac system. (See also: [[submitting bugs]])
'''Trac''' is an online system for tracking software bugs and organizing software development. OLPC uses an instance of trac, located at [http://dev.laptop.org/ dev.laptop.org], to coordinate all its official software development. Bugs, features, and other work items are entered into trac as '''trac tickets'''. This assigns the work a unique reference number, which can be used to track progress using the trac system. (See also: [[reporting bugs]])


= older suggestions not included in the above =
== Trac Usage Guidelines ==


[[User:Gregorio|Gregorio]] 10:45, 27 June 2008 (UTC)
[[User:Gregorio|Gregorio]] 10:45, 27 June 2008 (UTC)
Line 7: Line 7:
From Michael's notes on recent meeting: http://lists.laptop.org/pipermail/devel/2008-June/015749.html
From Michael's notes on recent meeting: http://lists.laptop.org/pipermail/devel/2008-June/015749.html


Please comment there or here. Once we are agreed on the conventions we should also link them from Trac per Bert's suggestion.
Please comment on that thread. Once we are agreed we can update this page and link them from Trac per Bert's suggestion.


In yesterday's software status meeting, we formulated some conventions
In yesterday's software status meeting, we formulated some conventions
for using Trac for the next few months. They are:
for using Trac for the next few months. They are:


⚫
2. Greg will record customer preference data according to whatever means he sees fit and will inform us of these data in regular meetings.
1. The release team - presently including me, Greg Smith, and Kim Quirk
will occasionally tag a ticket as 'blocks:8.2.0' to indicate that it
blocks the 8.2.0 release. Such tickets will be understood to be part
of our release criteria. If you think that a ticket should be so
marked, please poke us until we deal with it.


3. Kim wants a way to keep track of 'critical' bugs. Michael defined 'critical bugs' as those bugs which receive the most careful oversight by the release team. Shortly, the release team will invent a convention for identifying such bugs which permits their inclusion in reports. These reports will be listed on the frontpage of Trac.
⚫
2. Greg will record customer preference data according to whatever means
he sees fit and will inform us of these data in regular meetings.

3. Kim wants a way to keep track of 'critical' bugs. Michael defined
'critical bugs' as those bugs which receive the most careful oversight
by the release team. Shortly, the release team will invent a
convention for identifying such bugs which permits their inclusion in
reports. These reports will be listed on the frontpage of Trac.
4. People should indicate the release they _wish_ that changes would
4. People should indicate the release they _wish_ that changes would land in via the Milestone field.
land in via the Milestone field.

5. People should indicate their confidence that the changes _will_ land
by tagging tickets with strings like:

8.2.0:+ -- means that the change is "within reach" or, preferably,
has been included in a dist-olpc3-updates series build.
8.2.0:? -- the change is "in danger of missing the boat".

8.2.0:- -- the change is unlikely to be ready for release

(NB: Please be conservative in tagging things <rel>:+.)

⚫
6. When it's unambiguous, people should attach test results to tickets
with tags like:

⚫
joyride-2027:- -- the issue persists in joyride-2027
⚫
joyride-2029:+ -- the issue was not reproducible in joyride-2027

⚫
If appropriate, please also describe the test procedure that was
executed to generate the result.


⚫
6. When it's unambiguous, people should attach test results to tickets with tags like:
7. We have added a 'Needs Action' field to Trac with several states for
common actions (and various kinds of ignorance of what action is
needed.) Please use it. Let us know if we need to change the set of
actions.


⚫
joyride-2027:- -- the issue persists in joyride-2027
8. The 'priority' field is a place for component maintainers to say what
⚫
joyride-2029:+ -- the issue was not reproducible in joyride-2027
they think is important; however, we expect that our regular IRC
meetings and emails will be the primary vehicle for communicating
day-to-day priority information.


⚫
If appropriate, please also describe the test procedure that was executed to generate the result.
(NB: We may revisit the priority information decisions.)


Please comment freely.
Please comment freely.
Line 73: Line 35:
The OLPC wiki is configured to allow automatic linking to trac tickets using special markup. For example, this code:
The OLPC wiki is configured to allow automatic linking to trac tickets using special markup. For example, this code:


* &lt;trac&gt;1&lt;/trac&gt;
&lt;trac&gt;1&lt;/trac&gt;


renders as the a link to the page for trac ticket item number 1:
renders as the a link to the page for trac ticket item number 1:
⚫
: <trac>1</trac>


There is also [[Template:Ticket]] and [[Template:Trac]], not recommended; <nowiki>{{ticket|42}}</nowiki> renders as {{ticket|42}}.
⚫
* <trac>1</trac>




See also:
== See also ==


* [http://dev.laptop.org OLPC trac installation]
* [http://dev.laptop.org OLPC trac installation]
* [http://en.wikipedia.org/wiki/Trac trac wikipedia page]
* [http://en.wikipedia.org/wiki/Trac trac wikipedia page]
* [http://trac.edgewall.org/ Official trac site]
* [http://trac.edgewall.org/ Official trac site]
* [[Submitting bugs]]
* [[Reporting bugs]]
* [[Trac ticket workflow]]


[[Category:Developers]]
[[Category:Developers]]
[[Category:Software]]
[[Category:Software]]
[[Category:Trac]]

Latest revision as of 14:10, 1 December 2011

Trac is an online system for tracking software bugs and organizing software development. OLPC uses an instance of trac, located at dev.laptop.org, to coordinate all its official software development. Bugs, features, and other work items are entered into trac as trac tickets. This assigns the work a unique reference number, which can be used to track progress using the trac system. (See also: reporting bugs)

older suggestions not included in the above

Gregorio 10:45, 27 June 2008 (UTC)

From Michael's notes on recent meeting: http://lists.laptop.org/pipermail/devel/2008-June/015749.html

Please comment on that thread. Once we are agreed we can update this page and link them from Trac per Bert's suggestion.

In yesterday's software status meeting, we formulated some conventions for using Trac for the next few months. They are:

2. Greg will record customer preference data according to whatever means he sees fit and will inform us of these data in regular meetings.

3. Kim wants a way to keep track of 'critical' bugs. Michael defined 'critical bugs' as those bugs which receive the most careful oversight by the release team. Shortly, the release team will invent a convention for identifying such bugs which permits their inclusion in reports. These reports will be listed on the frontpage of Trac.

4. People should indicate the release they _wish_ that changes would land in via the Milestone field.

6. When it's unambiguous, people should attach test results to tickets with tags like:

joyride-2027:- -- the issue persists in joyride-2027 joyride-2029:+ -- the issue was not reproducible in joyride-2027

If appropriate, please also describe the test procedure that was executed to generate the result.

Please comment freely.

Regards,

Michael

Trac ticket wiki markup

The OLPC wiki is configured to allow automatic linking to trac tickets using special markup. For example, this code: 

 <trac>1</trac>

renders as the a link to the page for trac ticket item number 1:

<trac>1</trac>

There is also Template:Ticket and Template:Trac, not recommended; {{ticket|42}} renders as #42.


See also

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Trac&oldid=263338"