Re: [platform-debug-dev] Updated debug util plugin

[Curtis Windatt <Curtis_Windatt@xxxxxxxxxx>]

Do your best.

The goal of the verification is to get at least two pairs of eyes looking at any code change. It can help catch simple coding errors, missing documentation/copyright changes, and bugs. We don't expect it will catch everything, it simply improves the quality of our code. Verification is also a way to get introduced to new areas of the code base.

In general, we try to assign verification to someone who can do a reasonable job to verify. Another thing to try is to ask the bug reporter to try and test the fix. Even if you can't reproduce the problem, you can concentrate on the code change, looking for ways it might break.

For critical or last minutes fixes that require more testing, you can always ask another developer to help verify. According to the 3.4 end game plan http://www.eclipse.org/eclipse/development/freeze_plan_3.4.php another committer must +1 a report in RC1, and two committers must +1 the report for RC2 (it gets even more restrictive after that).

Curtis

Pawel Piech ---05/01/2008 10:29:54 AM---Thank You, the get involved page is a good overview and if I think of anything valuable to add I'll go ahead and do it. My spe

From:	Pawel Piech <pawel.piech@xxxxxxxxxxxxx>
To:	"Eclipse Platform Debug component developers list." <platform-debug-dev@xxxxxxxxxxx>
Date:	05/01/2008 10:29 AM
Subject:	Re: [platform-debug-dev] Updated debug util plugin

---

Thank You, the get involved page is a good overview and if I think of anything valuable to add I'll go ahead and do it. My specific question was just to clarify how bugs are verified, and according to the overview, they are verified with both a code inspection as well by executing product with the fix included and verifying that the bug is addressed. So I'm still wondering what is done in cases where verifying the behavior is difficult or not possible, like in case of intermittent problems or difficult environment setup?

Cheers,
Pawel

Curtis Windatt wrote:

http://www.eclipse.org/eclipse/debug/get_involved.php

This page describes the basic processes we use. Not sure if it will be in enough detail to answer your questions though. So go ahead and ask.

Also, as a new committer you should have been given commit rights to our webspace, so you can update the site if you think it is incomplete.
:extssh:@dev.eclipse.org:/cvsroot/org.eclipse www/eclipse/debug

We do have a wiki page http://wiki.eclipse.org/Debug but currently it only has links and a Debug FAQ on it. The wiki can be edited by anyone with a bugzilla account.

Curtis

Pawel Piech ---04/30/2008 09:49:49 PM---Thanks Mike and Curtis,


From:	Pawel Piech <pawel.piech@xxxxxxxxxxxxx>
To:	"Eclipse Platform Debug component developers list." <platform-debug-dev@xxxxxxxxxxx>
Date:	04/30/2008 09:49 PM
Subject:	Re: [platform-debug-dev] Updated debug util plugin

---




Thanks Mike and Curtis,
I had no idea that the build notes log was maintained in this way. I have a couple of other questions about verification, but first I should ask if there is a wiki page somewhere describing the debug group processes?
-Pawel

Curtis Windatt wrote:
In debug, we expect that when committers verify bugs, they will add an entry to the buildnotes of the plugin (eg. buildnotes_platform-debug.html). To make it easier to do so, we provide a simple plug-in that provides actions to insert new entries. You specify a bug number and the tool will grab the required information from bugzilla and format it properly.

We (Mike Rennie and I) just updated the tool so that it matches our current format and comes with a preset key-binding (Ctrl-Alt-V for verify). We also added an update site to our website to make it easy to download and install.

To install using p2:

In Eclipse, go to Help > Software Updates
Drag the URL from this e-mail or hit the add site button
http://www.eclipse.org/eclipse/debug/update
Expand the new site to find the Debug Utility
Hit install
Hit the restart button when prompted
In the perspectives you want to have the actions, go to Window > Customize Perspective and enable the Bugzilla group on the Commands tab.

To install without p2 you can follow the above steps but use the old update site manager. You can also download the plugin directly by going to http://www.eclipse.org/eclipse/debug/update in your browser.

Time to start assigning bugs to Pawel to verify :)

Curtis

---


_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-debug-dev

_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-debug-dev




---


_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-debug-dev
 

_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-debug-dev