[aperi-dev] Defect report

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[aperi-dev] Defect report

From: Tom Guinane <guinane@xxxxxxxxxx>
Date: Mon, 1 Oct 2007 12:27:20 -0700
Delivered-to: aperi-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/listinfo/aperi-dev>
List-help: <mailto:aperi-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/aperi-dev>, <mailto:aperi-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/aperi-dev>, <mailto:aperi-dev-request@eclipse.org?subject=unsubscribe>

Hi Hans,
You created the defect report query in the development meeting agenda. Per our discussion on today's call, can you see if the defect report can be adjusted so the defects are listed by severity and then priority? So, all the majors would be first sorted by priority, then the normals, then the enhancements last. This should allow us to see the most critical bugs first, right? Dave, correct me if that is not what you wanted.

Cheers, Tom
___________________________________________
Tom Guinane Aperi Project Lead IBM ARC 408-927-2104 guinane@xxxxxxxxxx http://www.eclipse.org/aperi/

Follow-Ups:
- Re: [aperi-dev] Defect report
  - From: Hans Lin

Prev by Date: [aperi-dev] Aperi Roadmap V7 - DRAFT
Next by Date: [aperi-dev] Bugzilla - how to get started
Previous by thread: [aperi-dev] Aperi Roadmap V7 - DRAFT
Next by thread: Re: [aperi-dev] Defect report
Index(es):
- Date
- Thread

Breadcrumbs