Ticket #1409: submissions.pod.patch
File submissions.pod.patch, 4.2 KB (added by Aninhumer, 12 years ago) |
---|
-
docs/submissions.pod
22 22 However, if you do know how to fix the problem you encountered, then think 23 23 about submitting a patch, or (see below) getting commit privileges. 24 24 25 =head1 How To SubmitA Patch25 =head1 How To Create A Patch 26 26 27 27 Try to keep your patches specific to a single change, and ensure that your 28 28 change does not break any tests. Do this by running C<make test>. If there is 29 29 no test for the fixed bug, please provide one. 30 30 31 =over32 33 =item 134 35 Create the patch.36 37 31 In the following examples, F<parrot> contains the Parrot distribution, and 38 32 F<workingdir> contains F<parrot>. The name F<workingdir> is just a placeholder 39 33 for whatever the distribution's parent directory is called on your machine. … … 97 91 98 92 =back 99 93 100 = item 294 =head1 How To Submit A Patch 101 95 96 =over 97 98 =item 1 99 102 100 Go to Parrot's ticket tracking system at 103 101 L<https://trac.parrot.org/parrot/>. Log in, or create an account if you 104 102 don't have one yet. 105 103 104 =item 2 105 106 If there is already a ticket for the bug or feature that your patch relates 107 to, just attach the patch directly to the ticket. 108 106 109 =item 3 107 110 108 Select "New Ticket" L<https://trac.parrot.org/parrot/newticket>. 111 Otherwise select "New Ticket" at the top of the site. 112 L<https://trac.parrot.org/parrot/newticket> 109 113 110 114 =item 4 111 115 112 Give a clear and concise Summary .116 Give a clear and concise Summary, and prefix it with a C<[PATCH]> identifier. 113 117 114 Prefix it with a C<[PATCH]> identifier.115 116 118 =item 5 117 119 118 120 The Description should contain an explanation of the purpose of the patch, and … … 128 130 129 131 =item 7 130 132 131 Check the box for "I have files to attach to this ticket" 133 Check the box for "I have files to attach to this ticket". Double-check 134 that you've actually done this, because it's easy to forget. 132 135 133 Double-check that you've actually done this, because it's easy to forget.134 135 136 B<DO NOT> paste the patch file content into the Description. 136 137 137 138 =item 8 … … 247 248 248 249 =head1 What Happens Next? 249 250 250 Trac creates a ticket for the submission, and you will receive an automatic reply 251 with details of the ticket identifier. This identifier should be used in all 252 furthercorrespondence concerning the submission.251 If you created a new ticket for the submission, you will be taken to the page 252 for the new ticket and can check on the progress of your submission there. 253 This identifier should be used in all correspondence concerning the submission. 253 254 254 Everyone on the list sees the submission, and can comment on it. A developer255 with SVN commit authority willcommit it to SVN once it is clear that it is the255 Everyone on Trac sees the submission, and can comment on it. A developer with 256 SVN commit authority can commit it to SVN once it is clear that it is the 256 257 right thing to do. 257 258 258 Even developers with SVN commit authority stick to this scheme for larger or 259 more complex changes, to allow time for peer review.259 However developers with SVN commit authority may not commit your changes 260 immediately if they are large or complex, to allow time for peer review. 260 261 261 You can check the progress of your submission at the Parrot bugs page 262 L<http://bugs6.perl.org/>. If you have trouble logging in try username C<guest> 263 with password C<guest>. 262 A list of active tickets can be found here: 263 L<http://trac.parrot.org/parrot/report/1> 264 264 265 A Parrot Bug Summary page is also available from266 L<http s://rt.perl.org/rt3/NoAuth/parrot/Overview.html>265 A list of all the unresolved patches is at: 266 L<http://trac.parrot.org/parrot/report/15> 267 267 268 A list of all the unresolved patches is at269 L<http://www.parrotcode.org/openpatches.html>270 271 268 =head1 Patches for the Parrot website 272 269 273 270 The L<http://www.parrot.org> website is hosted in a Drupal CMS. Submit … … 302 299 =item 4 303 300 304 301 Request commit access via the C<parrot-dev> mailing list, or via IRC 305 (#parrot on irc.parrot.org). The existing committers will discuss your request in306 the next couple of weeks.302 (#parrot on irc.parrot.org). The existing committers will discuss your 303 request in the next couple of weeks. 307 304 308 305 If approved, a metacommitter will update the permissions to allow you to commit 309 306 to Parrot; see C<RESPONSIBLE_PARTIES> for the current list. Welcome aboard!