Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cme-dev] Components/Owners for bugzilla?

Hi Andy,

Seems like a reasonable idea.

Let me suggest the following as other possible areas for consideration:
  • Concern modeling (Stan)--because it's a key area of functionality itself, and it fits with the 4-step use case we've talked about and included on the web site.
  • Artifacts.  For now, I'd subdivide into AJ (Andy), Ant (Matt), and Java (Harold).
  • Do we want a contact for test-related issues?  There are several people who could take this one on, obviously.
  • Extraction (Peri), because it will become a key area of functionality soon, so might as well go ahead and add it.
  • Components (several people could do this one), for tool developer kinds of issues.  Or maybe just call the category "Extending the CME issues".

Just a few ideas...

     Peri


Andrew Clement <CLEMAS@xxxxxxxxxx>
Sent by: cme-dev-admin@xxxxxxxxxxx

04/22/2004 04:24 AM

Please respond to
cme-dev
To
cme-dev@xxxxxxxxxxx
cc
Subject
[cme-dev] Components/Owners for bugzilla?






We need to determine the list of components and their owners for bugzilla CME reporting/tracking.  At the moment we have one component 'CME' and the default person who gets emailed for bugs raised against that component is cme-inbox@xxxxxxxxxxx (very useful!)

I think we should name coarse grained areas - I can't initially see any point in naming puma/conman/etc as individual components as the users/raisers won't know which underlying code to pick.  So I was thinking of components like:

Docs
User Interface
Composition
Query

I need default component owners too - I was possibly thinking of Peri for Query, BillH for Composition, Sian for User Interface and maybe Helen for Docs.  Of course, these are only the initial contacts - they are perfectly free to reassign the bugs as appropriate once they've done some initial analysis.

Comments?

Andy.

===
Andy Clement
CME Development

Back to the top