parrotcode: Parrot Submission Instructions | |
Contents | Documentation |
docs/submissions.pod - Parrot Submission Instructions
How to submit bug reports, patches and new files to Parrot.
If you encounter an error while working with Parrot, and don't understand what is causing it, then submit a bug report using the parrotbug utility. The simplest way to use it is to run
% ./parrotbug
in the distribution's root directory, and follow the prompts.
However, if you do know how to fix the problem you encountered, then think about submitting a patch.
Try to keep your patches specific to a single change, and ensure that your change does not break any tests.
In the following examples, parrot contains the Parrot distribution, and parrotdev contains parrot. The name parrotdev is just a placeholder for whatever the distribution's parent directory is called on your machine.
diff
diff
for each file. The diff
should be created in parrot. cd parrot
diff -u docs/submissions.pod docs/submissions.new > submissions.patch
-ub
.diff
diff
on the two directories to create your patch. The diff
should be created in parrotdev. cd parrotdev
diff -ur --exclude=CVS parrot parrot.new > docs.patch
--exclude=.DS_Store
.Prefix it with a [PATCH]
identifier.
Double-check that you've actually done this, because it's easy to forget.
DO NOT paste the patch file content into the body of the message.
You may wish to apply a patch submitted by someone else before the patch is incorporated into CVS.
For single diff
patches, copy the patch file to parrot, and run:
cd parrot
patch -p0 < single.patch
For recursive diff
patches, copy the patch file to parrotdev, and run:
cd parrotdev
patch -p0 < recursive.patch
If you have a new feature to add to Parrot, such as a new test.
Prefix it with a [NEW]
identifier.
Double-check that you've actually done this, because it's easy to forget.
DO NOT paste the content of the new file or files into the body of the message.
RT creates a ticket for the submission, and you will receive an auto reply with details of the ticket identifier. This identifier should be used in all further correspondence concerning the submission.
Everyone on the list sees the submission, and can comment on it. A developer with CVS commit authority will commit it to CVS once it is clear that it is the right thing to do.
Even those developers with CVS commit authority stick to this scheme for all but the most trivial of their own patches, to allow time for peer review of their changes.
You can check the progress of your submission at the Parrot bugs page http://bugs6.perl.org/. If you have trouble logging in try username guest
with password guest
.
A list of all the unresolved patches is at http://www.parrotcode.org/openpatches/.
Adapted by Michael Scott from a tutorial submitted by Aldo Calpini, with some additional remarks from Bruce Gray.
|