Trac conventions

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

For 8.2.0, these bugs can be found in [1].

Polish

In most releases, there are bugs which are easy to fix and which users would greatly appreciate but which are not severe enough to block the release.

     polish:8.2.0 -- A bug worth fixing if you can't fix a blocker.

For 8.2.0, these bugs can be found in [2].

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.)