Trac conventions: Difference between revisions
(remove confusing excess punctuation, box sets it off fine) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
| ⚫ | |||
== Blockers == |
|||
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 above. |
|||
| ⚫ | |||
5. To nominate a "release blocker" for a release, use the following tags: |
|||
blocks?:8.2.0 -- proposed release blocker |
blocks?:8.2.0 -- proposed release blocker |
||
| Line 13: | Line 8: | ||
blocks-:8.2.0 -- set by the release team to mark a rejected release blocker |
blocks-:8.2.0 -- set by the release team to mark a rejected release blocker |
||
| ⚫ | |||
== Milestone Field == |
|||
| ⚫ | |||
== Slippage == |
|||
| ⚫ | |||
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:+ -- means that the change is "within reach" or, preferably, has been included in a dist-olpc3-updates series build. |
||
| Line 19: | Line 21: | ||
8.2.0:- -- the change is unlikely to be ready for release |
8.2.0:- -- the change is unlikely to be ready for release |
||
Please be conservative in tagging things <rel>:+ |
|||
== Simple Test Results == |
|||
| ⚫ | |||
| ⚫ | |||
joyride-2027:- -- the issue persists in joyride-2027 |
joyride-2027:- -- the issue persists in joyride-2027 |
||
joyride-2029:+ -- the issue was not reproducible 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. |
|||
== Workflow Data == |
|||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
== Priority == |
|||
| ⚫ | |||
The 'priority' field is a place for component maintainers to say what 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. |
|||
(NB: We may revisit the priority information decisions.) |
|||
[[Category:Trac]] |
[[Category:Trac]] |
||
Revision as of 23:13, 18 August 2008
Blockers
The release team may 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, see section 5 below.
blocks?:8.2.0 -- proposed release blocker
blocks:8.2.0 -- set by the release team to mark an accepted release blocker
blocks-:8.2.0 -- set by the release team to mark a rejected release blocker
Milestone Field
People should indicate the release they _wish_ that changes would land in via the Milestone field.
Slippage
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
Please be conservative in tagging things <rel>:+
Simple Test Results
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.
Workflow Data
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.
More information is available at Trac ticket workflow for the present ticket workflows.
Priority
The 'priority' field is a place for component maintainers to say what 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.
(NB: We may revisit the priority information decisions.)