Contents

Connect to the Eclipse Repository

The easiest way to download the correct projects from CVS is to use our Debug project set file. Download the psf file then in Eclipse go to File > Import... and select Team > Team Project Set. If you have not done so already, you will have to define a repository connection which can be done using the information below. The project set file will checkout the Debug projects from CVS. More information about project set files can be found on the project set file wiki page.

Create a CVS Repository Location with the following information:

Attribute name

Value

Host

dev.eclipse.org

Repository Path

/cvsroot/eclipse

User

anonymous

Password

(blank)

Connection Type

pserver

Use Default Port

On(default)

You can check projects out of the HEAD stream of the newly created repository location by selecting them, then Right Click > Check Out.

Your workspace setup is now complete. The Debug projects are set up to compile against your installed Eclipse plug-ins (the plug-ins that are being used by your currently running instance of Eclipse). This works because the Debug projects have the "Plug-in Dependencies" library on their Java build path.

When you upgrade your Eclipse install, the Debug projects will automatically compile against the new plugins. To compile against a different set of plug-ins, you can change the location in the preferences under Window > Preferences > Plug-in Development > Target Platform.

Creating Patches

So now you have the code to fix a bug in your host workspace and have tested it in your target. The next step is to get that code committed to CVS. However, only committers have the permission to do that. Instead, contributors are expected to create a patch file containing their changes and post it to the bug report they are working on. The patch will be reviewed by one or more committers. Once the patch is accepted, a committer will apply it to CVS and resolve the bug as fixed.

To create a patch, select all of the changed projects in the Package Explorer view. Right click and go to Team > Synchronize, this should open up the Synchronize View. In the Synchronize View, make sure there are no conflicting changes and that all of your changes follow the coding guidelines. Then select your outgoing changes, right click and go to Create Patch... In the dialog, select a destination for the patch (it is best to include the bug number in the file name and use the extension .patch), double check all your changes are included, then hit OK. Attach the created patch to the bug report.

Creating Bug Reports

When filing bugs against the Debug Project, we ask that you use your better judgment, and most importantly common sense before filing a bug.

Specifically:

Search bugzilla for existing bugs like yours BEFORE you file it. Resolving duplicates is time consuming.

Be sure that what happened is really a bug. For example if all you see is an entry in the log files that mentions Debug try to reproduce it, find out how it happened, or better yet come up with a test case. Some log entries are NOT bugs, and can be caused by incorrect workspace configuration, etc.

Bugzilla is not a forum. Do not ask questions on bugzilla like "how do I create a HelloWorld class?". This is not a bug.

Bugs should be filed against the PLATFORM-DEBUG or the JDT-DEBUG component. New feature requests should be filed with a severity of "enhancement".

By default, bugs filed against a Debug component will be assigned to an inbox account. Interested parties watch this inbox user to see incoming bugs. Committers or one of the Debug team leads move bugs from the inbox account when someone is actively working on a bug.

Bug Lifecycle

All bugs for the Debug components follow the same lifecycle. All committers and contributors must adhere to this lifecycle to ensure all defects are tracked and handled accordingly.

NEW - All newly filed bugs start out in the NEW state.

DUPLICATE/INVALID/WORKSFORME/WONTFIX - If a bug is a duplicate of another bug or if a Debug committer decides that no code changes will be made for the bug, the bug is resolved immediately with an explanation. Unless the bug is REOPENED for some reason, this is the end of the road.

ASSIGNED - Once a bug has been validated by a Debug committer, it is moved to the ASSIGNED state. When a committer is going to work on a bug, they typically reassign it to themselves.

RESOLVED-FIXED - Bugs are marked as RESOLVED-FIXED once a patch for the bug has been added to the bug report and committed to CVS. When requesting that someone verify a bug, we set the review flag for the person we want to verify it and add them to the CC list, if not already present. If for some reason the person you want to verify the bug does not have privileges to set the review flag, mention them in a comment asking to verify the bug and ensure they are on the CC list.

Bugzilla is picky about the state changes it allows, so we follow these steps to maximize efficiency:

Reassign the bug to the Debug committer who will fix the bug.

Create a patch of the proposed fixes for the bug and attach it to the bug report.

Commit the code changes to CVS.

Using the REVIEW flags add the other committer(s) who are to verify the bug (with the '?' flag).

Add the committer(s) involved in the review to the CC list - to ensure they are notified of a review request.

Mark the bug RESOLVED-FIXED with a request to verify.

VERIFIED-FIXED - Bugs are marked as VERIFIED-FIXED once someone verifies the fix that was checked into CVS. Bugs are always verified by a Debug committer other than the person who checked in the fix. The verifier makes sure that the original problem is fixed and also looks at the code for any obvious errors. This verification step ensures that all code changes are looked at by at least two pairs of eyes.

Bug Summary Tags

When bugs are triaged, a committer may add tags in square brackets to identify which feature the bug is related to. The tags currently being used are:

[viewmgmt]/[View Management] Auto-opening of views in perspective upon stat of debugging.

Test Passes

Before every milestone release the Debug team does an intense one-day test pass where we test all of the functionality of the Debug components. We try to check everything to make sure 100% of the functionality is available in every major release. In addition, we try odd use cases and unusual code to ensure our code is as robust as possible.

To organize the test pass, we follow a test script. The script defines a basic overview of what must be tested in each section.

If you would like to help out during a test pass, contact us via our mailing lists. Before the test pass, let us know what platform you are going to test on and what sections you are planning to test. If you have any questions about how to test some area, we would be happy to help explain.