Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Bug verification and reopening

In my experience (on the Eclipse Platform) code reviews are not frequent.... however, during the end-game (the final months leading up to a release) they become mandatory and more involved as the release gets closer. If you look at the some of notes about RCs (release candidates) on [1], you'll see what I mean.

I also noticed (anecdotally) that we tend to verify bugs more often during the end-game. Maybe I'm wrong on that.


On Wed, Oct 9, 2013 at 11:22 AM, John Arthorne <John_Arthorne@xxxxxxxxxx> wrote:
Rodrigo Rocha Gomes e Souza <rodrigorgs@xxxxxxxxx> wrote on 10/08/2013 12:47:55 PM:

> Hmm, interesting. Are the dates of the testing days documented
> anywhere (mailing list, wiki)?

It is generally the Tuesday of milestone week. When there are local holidays sometimes the schedule is shifted but that is the most common day.

> I'm assuming that most verifications correspond to manual testing,
> and that code review is not frequent. Is this a reasonable assumption?

I think most of the team uses "verified" to mean "confirm that the fix is in the build". The most preferred way is to try reproducing the original bug using the steps from the bug report, and related cases. Verifying by source inspection is usually a last resort when the problem is hard or impossible to reproduce (e.g., threading or locking problem, API documentation problem). If a code review happens it usually occurs before the fix is even released, so it is unrelated to the "verified" state in bugzilla.


eclipse-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

R. Ian Bull | EclipseSource Victoria | +1 250 477 7484 |

Back to the top