Changeset 139459 for trunk/doc-new


Ignore:
Timestamp:
Aug 17, 2015, 10:34:24 PM (3 years ago)
Author:
cal@…
Message:

guide: clarify what to do when taking over maintainership *and* fixing bugs

File:
1 edited

Legend:

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

    r134587 r139459  
    650650
    651651        <listitem>
    652           <para>Now, <ulink url="https://trac.macports.org/newticket">file
    653               a new ticket in Trac</ulink>. Set <guilabel>type</guilabel> to
    654             <guilabel>enhancement</guilabel> if you only changed the maintainer
    655             and an appropriate other type if you also fixed a bug or enhanced
    656             or updated the port. Leave the <guilabel>milestone</guilabel> field
    657             empty. If you added yourself as co-maintainer, add the other
    658             maintainers in the <guilabel>Cc</guilabel> field. Finally, fill in
    659             the <guilabel>port</guilabel> field, set
    660             <guilabel>keywords</guilabel> to <userinput>haspatch</userinput>
    661             (because you are attaching a patch), check the box that you want to
    662             attach files to the ticket and submit. After submission, attach the
    663             patch you created in the previous step.</para>
     652          <para>If you are only changing the maintainer, <ulink
     653              url="https://trac.macports.org/newticket">file a new ticket in
     654              Trac</ulink>. Set <guilabel>type</guilabel> to
     655            <guilabel>enhancement</guilabel>. Leave the
     656            <guilabel>milestone</guilabel> field empty. If you added yourself
     657            as co-maintainer, add the other maintainers in the
     658            <guilabel>Cc</guilabel> field. Finally, fill in the
     659            <guilabel>port</guilabel> field, set <guilabel>keywords</guilabel>
     660            to <userinput>haspatch</userinput> (because you are attaching
     661            a patch), check the box that you want to attach files to the ticket
     662            and submit. After submission, attach the patch you created in the
     663            previous step.</para>
     664
     665          <para>If you are also fixing a bug, attach a separate patch for that
     666            change to the same ticket. If you are fixing a bug that already has
     667            a ticket, attach a patch fixing the bug there and file the
     668            maintainer change in a separate ticket (with a separate patch) as
     669            discussed above. In general, please create a separate patch for
     670            each semantic change. Doing so enables each independent change to
     671            be accepted without worries about conflicts that sometimes arise
     672            when several changes are rolled into one patch and simplifies
     673            reviewing. Do not worry that you cannot change the
     674            <guilabel>keywords</guilabel> to <userinput>haspatch</userinput> on
     675            existing tickets.</para>
    664676        </listitem>
    665677
Note: See TracChangeset for help on using the changeset viewer.