Planning and Future Work
By Sub-Group / Contributor
|SPIRIT||Anthony Berent (Arm)|
|Memory||Ted Williams (Wind River)|
|DSF||Pawel Piech (Wind River)|
|Randy Rohrbach (Wind River)|
|Ted Williams (Wind River)|
|GDB||Veenu Verma (Ericsson)|
|Marc Khouzam (Ericsson)|
|Francois Chouinard (Ericsson)|
In addition to component selected from the component field, DD bugs are optionally categorized using the feature name that the bug affects. The feature names are listed in bug's summary in square brackets ('').
Following are the features currently used in the DD bug database:
- breakpoint support
- infrastructure (control, caches, etc.) for managing debugger back-end commands and their results
- utilities for asynchronous programming, mostly extending functionality from java.util.concurrent
- console view support
- debug view
- debug view (aka launch view) support
- disassembly view support
- user and design documentation (may need to split this feature)
- expressions view support
- launch configurations, delegates, UI, etc.
- memory view support
- modules view support
- number formats detail
- detail pane showing different number formats, used in variables, registers, and expressions views
- register view support
- run control
- support for run control commands
- infrastructure for registering, grouping, referencing services, based on OSGi services
- source lookup
- mapping debugger sources to the host file system, opening the editor
- stack display
- standard model
- compatibility with standard debug model
- support for browsing symbols in modules view
- unit tests
- update policy
- configurable update modes used in variables, expressions, registers views
- variables view support
- Features which exist in CDI-GDB integration but are missing in DSF-GDB.
- Bugs related to main menu, context menus, and toolbars.
Bug Life Cycle
Everybody - users and developers - may apply for a Bugzilla account and submit bug reports or enhancement requests.
Once the bug report is filed, contributors and committers work on it, including updates to bug status. All users may contribute to the discussion by adding comments (but typically not change the status fields). The Eclipse Process Guidelines contain some good information and a handy diagram for understanding the lifecycle of an issue in Bugzilla.
How bugs are ASSIGNED
- Normally a bug should be created and assigned to the DD inbox: email@example.com. However, when a developer creates a bug that he/she intends to work on, he may set the "Assigned To" field to himself. The project is configured to add firstname.lastname@example.org to bug's CC list, so all inbox listeners will get notified of the bug anyhow.
- If the bug is in the inbox, the component owner, which is normally the leader of the sub-project owns the component, confirms that the bug is valid and assigns it to a committer or contributor.
- Alternatively, if a contributor created the bug for an issue that was discovered and immediately fixed, the contributor should assign the bug to himself.
- Plan items and other composite enhancements can stay assigned to the inbox, but have their state changed to ASSIGNED when a commitment is made to fix them.
- When the contributor can commit to a fixing a bug, he changes the state to ASSIGNED and sets a target milestone.
How bugs are FIXED and VERIFIED
- When a committer or contributor has completed fixing the bug, he should post a patch with the fix to the bug.
- A committer commits the changes to CVS. A contributor can request a committer to apply the patch.
- The committer changes the "Assigned To" field of the bug to another committer who is to review the fix.
- The committer fixing the bug changes the bug status to FIXED.
- The reviewer should review the changes and optionally confirm program behavior and mark the bug as VERIFIED.
How bugs are CLOSED
- With each milestone build, the VERIFIED bugs are logged in build notes and marked as CLOSED.
=== Bugs in maintenance release
- We will only have maintenance releases for latest major release.
- If a bug is determined to be severe enough to be addressed in the maintenance release, that bug is to be re-opened and targeted for that release.
- Part of the bug review is to make sure that the fix is applied to both branches.