Changeset 33486 for trunk/doc-new


Ignore:
Timestamp:
Jan 27, 2008, 9:23:45 PM (12 years ago)
Author:
simon@…
Message:

doc-new: Whitespace only changes. Using spaces instead of tabs.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc-new/guide/xml/project.xml

    r33485 r33486  
    8181          log or it could break the page layout. Example:</para>
    8282
    83           <literallayout>{{{
     83          <literallayout>{{{
    8484<replaceable>your build log here</replaceable>
    8585}}}</literallayout>
     
    9393          <itemizedlist>
    9494            <listitem>
    95               <para><guimenu>High</guimenu> - Reserved for the use of MacPorts
    96               team members, as they are the best fit to determine which reports
    97               warrant a higher priority over others.</para>
     95              <para><guimenu>High</guimenu> - Reserved for the use of MacPorts
     96              team members, as they are the best fit to determine which
     97              reports warrant a higher priority over others.</para>
    9898            </listitem>
    9999
     
    110110
    111111            <listitem>
    112               <para><guimenu>Not set</guimenu> - Anything that doesn't fit the categories high,
    113               normal, or low.</para>
     112              <para><guimenu>Not set</guimenu> - Anything that doesn't fit the
     113              categories high, normal, or low.</para>
    114114            </listitem>
    115115          </itemizedlist>
     
    137137
    138138            <listitem>
    139               <para><guimenu>server/hosting</guimenu> - For MacPorts hosting &amp;
    140               server-side issues, reserved for MacPorts PortMgr team members.</para>
    141             </listitem>
    142 
    143             <listitem>
    144               <para><guimenu>website</guimenu> - MacPorts website enhancements and
     139              <para><guimenu>server/hosting</guimenu> - For MacPorts hosting
     140              &amp; server-side issues, reserved for MacPorts PortMgr team
     141              members.</para>
     142            </listitem>
     143
     144            <listitem>
     145              <para><guimenu>website</guimenu> - MacPorts website enhancements
     146              and error corrections.</para>
     147            </listitem>
     148
     149            <listitem>
     150              <para><guimenu>wiki</guimenu> - MacPorts Wiki enhancements and
    145151              error corrections.</para>
    146152            </listitem>
    147 
    148             <listitem>
    149               <para><guimenu>wiki</guimenu> - MacPorts Wiki enhancements and error
    150               corrections.</para>
    151             </listitem>
    152153          </itemizedlist>
    153154        </listitem>
     
    160161
    161162        <listitem>
    162           <para><guilabel>Cc:</guilabel> Anyone else besides the ticket reporter
    163           and assignee who would like to be kept involved in the development
    164           of the ticket, and/or the port maintainer in case his/her address does
    165           not appear in the <guimenu>Assign To</guimenu> drop down menu. Multiple
    166           emails should be separated with a comma (i.e. <literal>you@example.org,
    167           maintainer@macports.org</literal>). To get the maintainer email address
    168           use <command>port info &lt;portname&gt;</command>.</para>
     163          <para><guilabel>Cc:</guilabel> Anyone else besides the ticket
     164          reporter and assignee who would like to be kept involved in the
     165          development of the ticket, and/or the port maintainer in case
     166          his/her address does not appear in the <guimenu>Assign To</guimenu>
     167          drop down menu. Multiple emails should be separated with a comma
     168          (i.e. <literal>you@example.org, maintainer@macports.org</literal>).
     169          To get the maintainer email address use <command>port info
     170          &lt;portname&gt;</command>.</para>
    169171        </listitem>
    170172
     
    216218            </listitem>
    217219
    218             <listitem>
    219               <para>Blank - For unclassified tickets that don't fit into any
    220               of the provided milestones.</para>
    221             </listitem>
     220            <listitem>
     221              <para>Blank - For unclassified tickets that don't fit into any
     222              of the provided milestones.</para>
     223            </listitem>
    222224          </itemizedlist>
    223225        </listitem>
     
    237239
    238240        <listitem>
    239           <para><guilabel>Attachments:</guilabel> Files may be attached to a
    240           ticket when it is being created if the checkbox that reads
    241           &ldquo;I have files to attach to this ticket&rdquo; is selected,
    242           or after it has been submitted by using the file attachment button.</para>
     241          <para><guilabel>Attachments:</guilabel> Files may be attached to a
     242          ticket when it is being created if the checkbox that reads &ldquo;I
     243          have files to attach to this ticket&rdquo; is selected, or after it
     244          has been submitted by using the file attachment button.</para>
    243245        </listitem>
    244246      </itemizedlist>
     
    286288
    287289      <para>Enhancements to existing ports may comprise new functionality for
    288       a given port, bug fixes or even simple version updates. They should always
    289       be contributed as <filename>Portfile</filename> patches. See Ticket Submission
    290       Guidelines above for a description of all fields.</para>
     290      a given port, bug fixes or even simple version updates. They should
     291      always be contributed as <filename>Portfile</filename> patches. See
     292      Ticket Submission Guidelines above for a description of all
     293      fields.</para>
    291294
    292295      <orderedlist>
     
    301304
    302305        <listitem>
    303           <para>Set the type to <guilabel>enhancement</guilabel> for miscellaneous
    304           enhancements or to <guilabel>defect</guilabel> for bug fixes.</para>
    305         </listitem>
    306 
    307         <listitem>
    308           <para>Set the milestone to <guilabel>Port
    309           Enhancements</guilabel>, <guilabel>Port Updates</guilabel> or <guilabel>Port
    310           Bugs</guilabel> depending on the case.</para>
     306          <para>Set the type to <guilabel>enhancement</guilabel> for
     307          miscellaneous enhancements or to <guilabel>defect</guilabel> for bug
     308          fixes.</para>
     309        </listitem>
     310
     311        <listitem>
     312          <para>Set the milestone to <guilabel>Port Enhancements</guilabel>,
     313          <guilabel>Port Updates</guilabel> or <guilabel>Port Bugs</guilabel>
     314          depending on the case.</para>
    311315        </listitem>
    312316
Note: See TracChangeset for help on using the changeset viewer.