How to help with harvesting - Simple things we can all do
Last updated at 10:27 pm UTC on 19 March 2007
If you drop by on the squeak irc channel (irc.freenode.net:6667/#squeak) you will very probably find someone who can help you with questions you have about the Harvesting process. [Particularly during the "Squeak Chats" posted in the mailing list.]
In addition to Reporting Bugs and Fixes, there are things all of us can do to contribute to the long-term health of Squeak. If you don't already have one, create a new Mantis account then log in and select the "View Issues" link at the top of the page. The default filter will show you all open bugs for all projects. If you're just starting, focus on those in category "Squeak" or "Squeak Packages". Pick a bug report or fix that has had little or no activity and, depending on which it is...
Reporting on an existing Fix
Here are some things to consider. In each case you can note your findings on Mantis. This will help Squeak's maintainers process these fixes.
- Make sure the bug still exists in the latest alpha release. If the original reporter was not specific enough to permit you to reproduce their bug, place a note to that effect on Mantis.
- If the fix was submitted with a separate test, load the test and run it. Does it still fail? (comment on Mantis)
- If the fix was not submitted with SUnit tests, and you feel you understand the bug well, try to write one and submit it as an attachment with a note.
- Load the fix into the most recent development image. Comment on mantis if it does not load properly or causes serious problems after loading.
- Does the fix appear to actually work?
- Is the fix in the proper "gzipped changeset" format? If not, attach a version that is.
- Is new code introduced by the fix commented?
Updating a Bug Report
- Use the search tool to see if this is a duplicate of another bug. Mark it if it is (be sure to check to see if it is a regression: a fixed bug that has returned in a later release). Comment on your findings. Be sure to reference the older bug report if you feel that this is a duplicate.
- Verify that this bug still exists. Find out by testing to see if the bug exists in the latest alpha release. If the original reporter was not specific enough to permit you to reproduce their bug, place a note to that effect on Mantis.
- Did the bug report include SUnit tests? If not, and you feel you understand the bug well, try to write one and submit it as an attachment with a note.
Commenting on enhancements
- Try loading the enhancement into the latest alpha release and report any problems.
- Does the enhancement seem to work as advertised?
- If this is a UI enhancement, make aesthetic comments as appropriate
- Is the enhancement in the proper "gzipped changeset" format? If not, attach a version that is.
- Is new code introduced by the enhancement commented?
Submitting class/method comment fixes and additions
- If you understand an uncomment class well enough to add a comment, do so and submit your comment as a changeset.
Keeping your own reports up to date
If you've had second thoughts about a bug or fix you've reported, please update the Mantis entry accordingly.
