Change Description Template
From OpenLaszlo
Fill in as much of this as makes sense. For external contributors, you don't yet have access to bug numbers, and you won't have any reviewers when you first submit a patch.
Summary: Integrate development tools New Features: Feature LPP-1234: Over-torqued wing nuts should be disallowed Bugs Fixed: Bug LPP-5678: Only right-handed gimlets are supported Technical Reviewer: frodo@bag-end.com (verbal) QA Reviewer: trinity@matrix.net (regression tests passed) Doc Reviewer: arnold@t3.org (Message-Id: <20030708183546.B0B4F58245@icicle.pobox.com>) Documentation: Attempts to tighten wing nuts excessively will be automatically prevented by sending a 40kv pulse to the nut wings. Release Notes: Both left- and right-handed gimlets are supported for adjusting framus levels. Details: Tests:
| Field | Description |
|---|---|
| Summary | Summary of the change. |
| New Features | One line descriptions of new features in this change, give RFE number if appropriate. |
| Bugs Fixed | Bug number and bug summary for each bug fixed in this change. |
| Reviewers | Each of the reviewer fields should contain an email address and some description of what the review consisted of. |
| Documentation | Prototype documentation for each new feature. |
| Release Notes | Prototype release notes for each bug fixed. |
| Details | Any additional information. Changes to the build procedure, implementation changes that other developers need to be aware of. |
| Tests | A description of how this change was tested. |
N.B.: Please list the features and bugs fixed in the format:
Feature <the bug number> <the bug 1-liner>
or
Bug <the bug number> <the bug 1-liner>
1 per line, for each bug fixed in the check-in. This makes it much easier for the integrator and QA to grep for what bugs they should be documenting/closing/verifying.
