Changes between Version 23 and Version 24 of NewParrotDeveloperGuide
- Timestamp:
- 12/03/10 15:42:23 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NewParrotDeveloperGuide
v23 v24 13 13 * [http://perldoc.perl.org/perldoc.html perldoc] (provided by package {{{perl-doc}}} on Debian/Ubuntu). 14 14 * [http://git-scm.com/ git] 15 * [http://freshmeat.net/projects/diffstat/ diffstat]16 15 17 16 == Getting Parrot == … … 111 110 == Submitting your work == 112 111 113 Once again there is a POD covering this topic. Read [https://github.com/parrot/parrot/blob/master/docs/submissions.pod docs/submissions.pod] for specific details on how to submit your work. In general you'll need to create a patch and then email that patch to perlbug.112 In general you'll need to create a patch and then create a ticket on Parrot's [http://trac.parrot.org/parrot/report/1 ticket tracking system]. Give as much details as you can. A good idea is to provide a list of all files affected with summary of the changes made in each file and the reasons that made you change them. And don't forget to attach your patch directly to the ticket. 114 113 115 114 {{{ 116 115 ~$ git status 116 ~$ git diff --stat 117 117 ~$ git diff > names_test_rewrite.patch 118 ~$ diffstat names_test_rewrite.patch119 names.t | 63 +++++++++++++++++++++++++++++++++------------------------------120 1 file changed, 33 insertions(+), 30 deletions(-)121 118 }}} 122 119 120 Once again there is a POD covering this topic. Read [https://github.com/parrot/parrot/blob/master/docs/submissions.pod docs/submissions.pod] for specific details on how to submit your work. 121 123 122 [http://www.perlfoundation.org/parrot/index.cgi/names_test_rewrite.patch?action=attachments_download;page_name=starting_at_the_bottom;id=20081113142750-0-29058 names_test_rewrite.patch] 124 125 '''''This section is outdated, and refers to our old RT system; it should be updated to refer to trac. (Or just removed in favor of updating the POD in the repo.'''''126 127 128 Then you'll need to send an email, with the patch as an attachment, to Parrotbug. It should look something like this.129 130 {{{131 from Your Name <your.name at gmail.com>132 to parrotbug at parrotcode.org133 subject [PATCH] rewrite of names.t to PIR134 135 This is a rewrite of t/oo/names.t from a perl test to a PIR test136 137 names.t | 63 +++++++++++++++++++++++++++++++++------------------------------138 1 file changed, 33 insertions(+), 30 deletions(-)139 140 --141 }}}142 143 Parrotbug will autoreply to your submission with an RT Ticket Id. Here's an example of a typical response.144 145 {{{146 Greetings,147 148 This message has been automatically generated in response to the149 creation of a parrotbug regarding:150 "[PATCH] rewrite of names.t to PIR"151 152 There is no need to reply to this message right now. Your ticket has been153 assigned an ID of [perl #60512].154 155 Please include the string:156 [perl #60512]157 In the subject line of all future correspondence about this issue. To do so,158 you may reply to this message.159 160 Thank you,161 parrotbug162 163 http://rt.perl.org/rt3/Ticket/Display.html?id=60512164 }}}165 166 It's that simple.167