Changeset 82805


Ignore:
Timestamp:
Aug 20, 2011, 10:32:01 PM (8 years ago)
Author:
jmr@…
Message:

guide: rephrase ticket guidelines to encourage using attachments for lengthy output, and request compression for large files

File:
1 edited

Legend:

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

    r80901 r82805  
    124124          <literallayout>
    125125{{{
    126 <replaceable>your build log here</replaceable>
     126<replaceable>your error message here</replaceable>
    127127}}}
    128128          </literallayout>
    129129
    130           <para>Submitters are advised to trim pastes and logs of any kind to
     130          <para>Submitters are advised to trim inline pastes and logs to
    131131          what's really relevant to the report, as otherwise overly large
    132           submissions that might contain redundant and/or unnecessary
    133           information might become unmanageable. If it is truly necessary to
    134           include long output, use an attachment, don't paste it inline.
     132          ticket pages can become unmanageable. Long output, such as the
     133          full log from a port build, should be added as an attachment, not
     134          pasted inline. See "I have files to attach to this ticket" below.
    135135          </para>
    136136
     
    302302          you create it. Or you can attach files later using the
    303303          <guilabel>Attach File</guilabel> button.</para>
     304          <para>If the file you are attaching is larger than 256 KiB, please
     305          compress it with bzip2 or gzip first to save space on the server and
     306          bandwidth for those downloading it, as
     307          Trac will not preview files above that size anyway.</para>
    304308        </listitem>
    305309      </itemizedlist>
Note: See TracChangeset for help on using the changeset viewer.