Changes between Initial Version and Version 1 of IetfSpecificFeatures

09/07/08 14:34:38 (14 years ago)



  • IetfSpecificFeatures

    v1 v1  
     1= IETF-Specific Features =
     3This Trac installation has a few IETF-specific features which are not generally found
     4in Trac:
     6 * Occurences of RFC numbers or draft names in Wiki text will generate links to the
     7   RFC or draft in question.  Unless you want to point to an RFC or draft in a
     8   specific location which is different from the automatically generated link, you
     9   don't need to explicitly add links for RFCs and drafts.
     11 * Each issue in the issue tracker can be indicated to concern a 'component'. This is
     12   a standard Trac feature; however, the list of available components is automatically
     13   updated to include all the active working group drafts.  This makes it easier to
     14   associate issues with drafts for the WG participants, without the Chairs needing to
     15   go in as admin users and add a new component each time there's a new WG draft.
     17 * The 'Severity' field of an issue has a special significance if the issue type is
     18   set to 'state' or 'task'.  In that case, the Severity will be shown as an
     19   annotation to the draft state on the regular WG status page on
     20   This can be useful for WG chairs to indicate more exactly the state of a WG draft,
     21   which will otherwise simply be indicated as 'Active' on the status page, until it
     22   is sent to the IESG for processing.
     24 * If issues are registered against a draft ,indicated by setting the issue's
     25   'component' field to the appropriate (abbreviated) draft name, the status page
     26   will show a progress bar, indicating the total number of issues for that draft, as
     27   well as the proportion which have been closed, and the number of still open issues.