[actf-dev] Proposed bug convention

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

[actf-dev] Proposed bug convention

From: Michael A Squillace <masquill@xxxxxxxxxx>
Date: Thu, 5 Jun 2008 13:23:26 -0500
Delivered-to: actf-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/actf-dev>
List-help: <mailto:actf-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/actf-dev>, <mailto:actf-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/actf-dev>, <mailto:actf-dev-request@eclipse.org?subject=unsubscribe>

All:
I would like to propose that, to make searches on bug reports easier, we adopt the convention of putting the feature or product name in the bug summary. For instance:

javaco: <description of bug>
accprobe: <description of bug
aiBrowser: <description of bug

The bugzilla component category is too broad to make searching effective and, using this approach, we can search by keyword.

The current list of prefixes, I think, is:

accprobe - Accessibility Probe
aiBrowser - aiBrowser multi-media browser
adesigner: ADesigner
javaco: Java Validation Componentry
webelo - web validation componentry

Please add others as you see fit.
Thanks,

--> Mike Squillace
IBM Human Ability and Accessibility Center
Austin, TX

W:512.823.7423
M:512.970.0066

masquill@xxxxxxxxxx
www.ibm.com/able

Prev by Date: [actf-dev] Plugin structure changed
Next by Date: [actf-dev] Welcome Phani Kommareddy as a new technology.actf Committer
Previous by thread: [actf-dev] Plugin structure changed
Next by thread: [actf-dev] Welcome Phani Kommareddy as a new technology.actf Committer
Index(es):
- Date
- Thread

Breadcrumbs