<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>[50255] trunk/doc-new/guide/xml/project.xml</title>
</head>
<body>
<style type="text/css"><!--
#msg dl.meta { border: 1px #006 solid; background: #369; padding: 6px; color: #fff; }
#msg dl.meta dt { float: left; width: 6em; font-weight: bold; }
#msg dt:after { content:':';}
#msg dl, #msg dt, #msg ul, #msg li, #header, #footer, #logmsg { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; }
#msg dl a { font-weight: bold}
#msg dl a:link { color:#fc3; }
#msg dl a:active { color:#ff0; }
#msg dl a:visited { color:#cc6; }
h3 { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; font-weight: bold; }
#msg pre { overflow: auto; background: #ffc; border: 1px #fa0 solid; padding: 6px; }
#logmsg { background: #ffc; border: 1px #fa0 solid; padding: 1em 1em 0 1em; }
#logmsg p, #logmsg pre, #logmsg blockquote { margin: 0 0 1em 0; }
#logmsg p, #logmsg li, #logmsg dt, #logmsg dd { line-height: 14pt; }
#logmsg h1, #logmsg h2, #logmsg h3, #logmsg h4, #logmsg h5, #logmsg h6 { margin: .5em 0; }
#logmsg h1:first-child, #logmsg h2:first-child, #logmsg h3:first-child, #logmsg h4:first-child, #logmsg h5:first-child, #logmsg h6:first-child { margin-top: 0; }
#logmsg ul, #logmsg ol { padding: 0; list-style-position: inside; margin: 0 0 0 1em; }
#logmsg ul { text-indent: -1em; padding-left: 1em; }#logmsg ol { text-indent: -1.5em; padding-left: 1.5em; }
#logmsg > ul, #logmsg > ol { margin: 0 0 1em 0; }
#logmsg pre { background: #eee; padding: 1em; }
#logmsg blockquote { border: 1px solid #fa0; border-left-width: 10px; padding: 1em 1em 0 1em; background: white;}
#logmsg dl { margin: 0; }
#logmsg dt { font-weight: bold; }
#logmsg dd { margin: 0; padding: 0 0 0.5em 0; }
#logmsg dd:before { content:'\00bb';}
#logmsg table { border-spacing: 0px; border-collapse: collapse; border-top: 4px solid #fa0; border-bottom: 1px solid #fa0; background: #fff; }
#logmsg table th { text-align: left; font-weight: normal; padding: 0.2em 0.5em; border-top: 1px dotted #fa0; }
#logmsg table td { text-align: right; border-top: 1px dotted #fa0; padding: 0.2em 0.5em; }
#logmsg table thead th { text-align: center; border-bottom: 1px solid #fa0; }
#logmsg table th.Corner { text-align: left; }
#logmsg hr { border: none 0; border-top: 2px dashed #fa0; height: 1px; }
#header, #footer { color: #fff; background: #636; border: 1px #300 solid; padding: 6px; }
#patch { width: 100%; }
#patch h4 {font-family: verdana,arial,helvetica,sans-serif;font-size:10pt;padding:8px;background:#369;color:#fff;margin:0;}
#patch .propset h4, #patch .binary h4 {margin:0;}
#patch pre {padding:0;line-height:1.2em;margin:0;}
#patch .diff {width:100%;background:#eee;padding: 0 0 10px 0;overflow:auto;}
#patch .propset .diff, #patch .binary .diff {padding:10px 0;}
#patch span {display:block;padding:0 10px;}
#patch .modfile, #patch .addfile, #patch .delfile, #patch .propset, #patch .binary, #patch .copfile {border:1px solid #ccc;margin:10px 0;}
#patch ins {background:#dfd;text-decoration:none;display:block;padding:0 10px;}
#patch del {background:#fdd;text-decoration:none;display:block;padding:0 10px;}
#patch .lines, .info {color:#888;background:#fff;}
--></style>
<div id="msg">
<dl class="meta">
<dt>Revision</dt> <dd><a href="http://trac.macports.org/changeset/50255">50255</a></dd>
<dt>Author</dt> <dd>jmr@macports.org</dd>
<dt>Date</dt> <dd>2009-04-28 02:34:54 -0700 (Tue, 28 Apr 2009)</dd>
</dl>
<h3>Log Message</h3>
<pre>Update guide to reflect Trac changes.</pre>
<h3>Modified Paths</h3>
<ul>
<li><a href="#trunkdocnewguidexmlprojectxml">trunk/doc-new/guide/xml/project.xml</a></li>
</ul>
</div>
<div id="patch">
<h3>Diff</h3>
<a id="trunkdocnewguidexmlprojectxml"></a>
<div class="modfile"><h4>Modified: trunk/doc-new/guide/xml/project.xml (50254 => 50255)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/doc-new/guide/xml/project.xml 2009-04-28 09:10:31 UTC (rev 50254)
+++ trunk/doc-new/guide/xml/project.xml 2009-04-28 09:34:54 UTC (rev 50255)
</span><span class="lines">@@ -111,10 +111,11 @@
</span><span class="cx"> <para><guilabel>Description:</guilabel> All details that might
</span><span class="cx"> be relevant to someone reading the ticket. <ulink
</span><span class="cx"> url="http://trac.macports.org/wiki/WikiFormatting">Wiki
</span><del>- formatting</ulink> or attached log files should be used for large
- text blocks. If you want to post a build log make sure you use
- <literal>{{{<replaceable>...</replaceable>}}}</literal> around the
- log or it could break the page layout. Example:</para>
</del><ins>+ formatting</ulink> should be used to ensure that text is formatted
+ correctly. Use the Preview button before submitting. If you want to
+ post preformatted text such as a log or terminal output, make sure
+ you use <literal>{{{<replaceable>...</replaceable>}}}</literal>
+ around the text or it could break the page layout. Example:</para>
</ins><span class="cx">
</span><span class="cx"> <literallayout>
</span><span class="cx"> {{{
</span><span class="lines">@@ -122,15 +123,17 @@
</span><span class="cx"> }}}
</span><span class="cx"> </literallayout>
</span><span class="cx">
</span><del>- <para>Submitters are advised to trim pastes and logs of any kind to what's
- really relevant to the report, as otherwise overly large submissions that
- might contain redundant and/or unnecessary information might become unmanageable.
</del><ins>+ <para>Submitters are advised to trim pastes and logs of any kind to
+ what's really relevant to the report, as otherwise overly large
+ submissions that might contain redundant and/or unnecessary
+ information might become unmanageable. If it is truly necessary to
+ include long output, use an attachment, don't paste it inline.
</ins><span class="cx"> </para>
</span><span class="cx">
</span><span class="cx"> </listitem>
</span><span class="cx">
</span><span class="cx"> <listitem>
</span><del>- <para><guilabel>Type:</guilabel> There are two main types of
</del><ins>+ <para><guilabel>Type:</guilabel> There are five types of
</ins><span class="cx"> tickets.</para>
</span><span class="cx">
</span><span class="cx"> <itemizedlist>
</span><span class="lines">@@ -144,6 +147,23 @@
</span><span class="cx"> patches, created to enhance something that isn't failing its
</span><span class="cx"> intended purpose.</para>
</span><span class="cx"> </listitem>
</span><ins>+
+ <listitem>
+ <para><guimenu>update</guimenu> - Tickets, with or without
+ patches, involving updating a port to a newer upstream
+ version.</para>
+ </listitem>
+
+ <listitem>
+ <para><guimenu>submission</guimenu> - Tickets created to submit
+ Portfiles for software not currently available in MacPorts.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para><guimenu>request</guimenu> - Tickets created to request
+ the creation of a new port.</para>
+ </listitem>
</ins><span class="cx"> </itemizedlist>
</span><span class="cx"> </listitem>
</span><span class="cx">
</span><span class="lines">@@ -177,59 +197,10 @@
</span><span class="cx"> </listitem>
</span><span class="cx">
</span><span class="cx"> <listitem>
</span><del>- <para><guilabel>Milestone:</guilabel> This is a ticket category that
- allows for search and sorting tickets efficiently.</para>
-
- <itemizedlist>
- <listitem>
- <para><guimenu>MacPorts x.y.z</guimenu> - for base-level
- tickets which have been assigned to a particular future
- release of MacPorts.</para>
- </listitem>
-
- <listitem>
- <para><guimenu>MacPorts Future</guimenu> - for base-level
- tickets which are still under consideration and have not
- yet been assigned to a specific future release of
- MacPorts.</para>
- </listitem>
-
- <listitem>
- <para><guimenu>Port Bugs</guimenu> - for tickets reporting or
- fixing bugs in ports provided by MacPorts.</para>
- </listitem>
-
- <listitem>
- <para><guimenu>Port Enhancements</guimenu> - for submissions
- providing enhancements to ports provided by MacPorts.</para>
- </listitem>
-
- <listitem>
- <para><guimenu>Port Requests</guimenu> - for requests for ports
- to be added to MacPorts.</para>
- </listitem>
-
- <listitem>
- <para><guimenu>Port Submissions</guimenu> - for submissions that
- add a port to MacPorts.</para>
- </listitem>
-
- <listitem>
- <para><guimenu>Port Updates</guimenu> - for submissions that
- update a port provided by MacPorts.</para>
- </listitem>
-
- <listitem>
- <para><guimenu>Website &amp; Documentation</guimenu> - for
- tickets relating to the documentation for MacPorts, including
- the MacPorts guide, Wiki, man pages and the website.</para>
- </listitem>
-
- <listitem>
- <para>Blank - For unclassified tickets that don't fit into any
- of the provided milestones.</para>
- </listitem>
- </itemizedlist>
</del><ins>+ <para><guilabel>Milestone:</guilabel> This is a ticket label that
+ indicates that the ticket is intended to be fixed in a particular
+ MacPorts release. Leave it blank; it will be set by a project member
+ if appropriate.</para>
</ins><span class="cx"> </listitem>
</span><span class="cx">
</span><span class="cx"> <listitem>
</span><span class="lines">@@ -286,15 +257,30 @@
</span><span class="cx"> reporter and assignee who would like to be kept involved in the
</span><span class="cx"> development of the ticket. Multiple email addresses should be
</span><span class="cx"> separated with a comma and a space
</span><del>- (i.e. <literal>you@example.org, maintainer@macports.org</literal>).
- If you do not see the the <guilabel>Assign to:</guilabel> field
- (currently only committers can set <guilabel>Assign to:</guilabel>),
- add the email address of the port's maintainer(s) here; you can use
- <command>port info <replaceable>portname</replaceable></command>
- to find the maintainer for a port. Exclude the addresses
- <email>openmaintainer@macports.org</email> and
- <email>nomaintainer@macports.org</email> if they are listed.</para>
</del><ins>+ (i.e. <literal>you@example.org, maintainer@macports.org</literal>).</para>
+
+ <para>Most users will not be able to assign tickets. If this applies
+ to you, then when reporting port-related tickets, make sure you add
+ the port's maintainer to cc. Otherwise they may not notice the
+ ticket.</para>
</ins><span class="cx"> </listitem>
</span><ins>+
+ <listitem>
+ <para><guilabel>Assign To:</guilabel> Only users with commit access
+ can edit this field. If this is not you, see the section on the
+ <guimenu>Cc</guimenu> field above.</para>
+
+ <para>For tickets on ports, enter
+ the email address of the port's maintainer (use <command>port info
+ &lt;portname&gt;</command> to find this). If multiple maintainers
+ are listed, enter the first maintainer's email address here and
+ enter the remainining maintainers' email addresses in the
+ <guimenu>Cc</guimenu> field. Exclude the email address
+ <email>openmaintainer@macports.org</email> if it appears.
+ If the maintainer's email address is
+ <email>nomaintainer@macports.org</email>, leave the field
+ blank.</para>
+ </listitem>
</ins><span class="cx">
</span><span class="cx"> <listitem>
</span><span class="cx"> <para><guilabel>Port:</guilabel> For tickets on ports, enter the
</span><span class="lines">@@ -333,12 +319,11 @@
</span><span class="cx"> </listitem>
</span><span class="cx">
</span><span class="cx"> <listitem>
</span><del>- <para>Set the type to <guilabel>enhancement</guilabel>.</para>
</del><ins>+ <para>Set the type to <guilabel>submission</guilabel>.</para>
</ins><span class="cx"> </listitem>
</span><span class="cx">
</span><span class="cx"> <listitem>
</span><del>- <para>Set the milestone to <guilabel>Port
- Submissions</guilabel>.</para>
</del><ins>+ <para>Set the component to <guilabel>ports</guilabel>.</para>
</ins><span class="cx"> </listitem>
</span><span class="cx">
</span><span class="cx"> <listitem>
</span><span class="lines">@@ -369,14 +354,12 @@
</span><span class="cx">
</span><span class="cx"> <listitem>
</span><span class="cx"> <para>Set the type to <guilabel>enhancement</guilabel> for
</span><del>- miscellaneous enhancements or to <guilabel>defect</guilabel> for bug
- fixes.</para>
</del><ins>+ miscellaneous enhancements, to <guilabel>defect</guilabel> for bug
+ fixes, or to <guilabel>update</guilabel> for version updates.</para>
</ins><span class="cx"> </listitem>
</span><span class="cx">
</span><span class="cx"> <listitem>
</span><del>- <para>Set the milestone to <guilabel>Port Enhancements</guilabel>,
- <guilabel>Port Updates</guilabel> or <guilabel>Port Bugs</guilabel>
- depending on the case.</para>
</del><ins>+ <para>Set the component to <guilabel>ports</guilabel>.</para>
</ins><span class="cx"> </listitem>
</span><span class="cx">
</span><span class="cx"> <listitem>
</span></span></pre>
</div>
</div>
</body>
</html>