Changes between Version 2 and Version 3 of IetfSpecificFeatures
- Timestamp:
- 11/05/10 11:06:47 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
IetfSpecificFeatures
v2 v3 9 9 to http://tools.ietf.org/newpasswd . 10 10 11 The login and password is also used for commits to the SVN repository. See more about 12 the repository further down. 13 11 14 == IETF-Specific Features == 12 15 … … 17 20 RFC or draft in question. Unless you want to point to an RFC or draft in a 18 21 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 20 24 21 25 * Each issue in the issue tracker can be indicated to concern a 'component'. This is … … 50 54 once Trac has been installed. 51 55 56 For each WG with a Trac instance there is also a SVN repository, with an URL of the 57 form '''''!http://svn.tools.ietf.org/svn/wg/<wg>'''''. Anybody can check out from 58 the repository, but you need to use the tools server login and password in order to 59 commit to the repository. 52 60 61 The IETF Trac instances use a variation of the Trac SVN hook script which is provided 62 with Trac. This script updates Track Issue Tickets based on keywords in the SVN 63 commit messages; the keywords and their use is described in SvnTracHooks.