[Tinyos-2-commits] CVS: tinyos-2.x/doc/html tep1.html, 1.1.2.6, 1.1.2.7

[Phil Levis]

Update of /cvsroot/tinyos/tinyos-2.x/doc/html
In directory sc8-pr-cvs10.sourceforge.net:/tmp/cvs-serv21024/html

Modified Files:
      Tag: tinyos-2_0_devel-BRANCH
	tep1.html 
Log Message:
HTML


Index: tep1.html
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/html/tep1.html,v
retrieving revision 1.1.2.6
retrieving revision 1.1.2.7
diff -C2 -d -r1.1.2.6 -r1.1.2.7
*** tep1.html	27 Jun 2006 20:23:04 -0000	1.1.2.6
--- tep1.html	18 Oct 2006 05:29:56 -0000	1.1.2.7
***************
*** 304,310 ****
  <tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">18-Oct-2004</td>
  </tr>
! <tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.1.2.3</td>
  </tr>
! <tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2006-06-13</td>
  </tr>
  <tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List &lt;tinyos-devel at mail.millennium.berkeley.edu&gt;</td>
--- 304,310 ----
  <tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">18-Oct-2004</td>
  </tr>
! <tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.1.2.4</td>
  </tr>
! <tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2006-10-18</td>
  </tr>
  <tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List &lt;tinyos-devel at mail.millennium.berkeley.edu&gt;</td>
***************
*** 439,442 ****
--- 439,444 ----
  &quot;Obsolete&quot; because it has been replaced by another TEP, then the new
  TEP number should follow &quot;Obsolete,&quot; such as &quot;Obsolete by TEP 1231.&quot;</p>
+ <p>Once a TEP has the status &quot;Final,&quot; no part of it may change except
+ for the Status field. The Status field may only change to Obsolete.</p>
  <p>If a TEP is Best Current Practices or Documentary, then it MUST
  include an additional field, &quot;TinyOS-Version:,&quot; which states what
***************
*** 444,450 ****
  to all versions of TinyOS, until made obsolete by a future TEP. This
  field MUST appear after the Status field and before the Author field.</p>
! <p>The final required field is Author, which states the names of the
  authors of the document. Full contact information should not be listed
  here (see Section 3.2).</p>
  <p>If a TEP is a Draft, then four additional fields MUST be included:
  Draft-Created, Draft-Modified, Draft-Version, and Draft-Discuss.
--- 446,457 ----
  to all versions of TinyOS, until made obsolete by a future TEP. This
  field MUST appear after the Status field and before the Author field.</p>
! <p>The final required field is &quot;Author,&quot; which states the names of the
  authors of the document. Full contact information should not be listed
  here (see Section 3.2).</p>
+ <p>There is an optional field, &quot;Extends.&quot; The &quot;Extends&quot; field refers to
+ another TEP. The purpose of this field is to denote when a TEP represents
+ an addition to an existing TEP. Meeting the requirements of a TEP with an
+ Extends field requires also meeting the requirements of all TEPs listed
+ in the Extends field.</p>
  <p>If a TEP is a Draft, then four additional fields MUST be included:
  Draft-Created, Draft-Modified, Draft-Version, and Draft-Discuss.