Changes between Version 2 and Version 3 of IetfSpecificFeatures


Ignore:
Timestamp:
May 11, 2010, 4:06:47 AM (10 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • IetfSpecificFeatures

    v2 v3  
    99to http://tools.ietf.org/newpasswd .
    1010
     11The login and password is also used for commits to the SVN repository.  See more about
     12the repository further down.
     13
    1114== IETF-Specific Features ==
    1215
     
    1720   RFC or draft in question.  Unless you want to point to an RFC or draft in a
    1821   specific location which is different from the automatically generated link, you
    19    don't need to explicitly add links for RFCs and drafts.
     22   don't need to explicitly add links for RFCs and drafts.  Examples: RFC 2026,
     23   draft-ietf-poised95-std-proc-3
    2024
    2125 * Each issue in the issue tracker can be indicated to concern a 'component'. This is
     
    5054once Trac has been installed.
    5155
     56For each WG with a Trac instance there is also a SVN repository, with an URL of the
     57form '''''!http://svn.tools.ietf.org/svn/wg/<wg>'''''.  Anybody can check out from
     58the repository, but you need to use the tools server login and password in order to
     59commit to the repository.
    5260
     61The IETF Trac instances use a variation of the Trac SVN hook script which is provided
     62with Trac.  This script updates Track Issue Tickets based on keywords in the SVN
     63commit messages; the keywords and their use is described in SvnTracHooks.