Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cme-dev] Re: cme-dev digest, Vol 1 #5 - 8 msgs

I would like to unsubscribe from this list and am not sure I
see a way to do this via web. Please advise.
Ev



cme-dev-request@xxxxxxxxxxx wrote:

Send cme-dev mailing list submissions to
	cme-dev@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
	http://dev.eclipse.org/mailman/listinfo/cme-dev
or, via email, send a message with subject or body 'help' to
	cme-dev-request@xxxxxxxxxxx

You can reach the person managing the list at
	cme-dev-admin@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of cme-dev digest..."


Today's Topics:

   1. Components/Owners for bugzilla? (Andrew Clement)
   2. Re: Components/Owners for bugzilla? (Sian Whiting1)
   3. Re: Components/Owners for bugzilla? (Helen Hawkins)
   4. Context sensitive menu actions for certain queries (Matt Chapman)
   5. Re: Components/Owners for bugzilla? (Stan Sutton)
   6. Need to be able to cancel concern model building. (Matt Chapman)
   7. Re: Components/Owners for bugzilla? (Peri Tarr)
   8. Re: Components/Owners for bugzilla? (Bill Harrison)

--__--__--

Message: 1
To: cme-dev@xxxxxxxxxxx
From: Andrew Clement <CLEMAS@xxxxxxxxxx>
Date: Thu, 22 Apr 2004 09:24:53 +0100
Subject: [cme-dev] Components/Owners for bugzilla?
Reply-To: cme-dev@xxxxxxxxxxx

This is a multipart message in MIME format.
--=_alternative 002D4A6780256E7E_=
Content-Type: text/plain; charset="US-ASCII"

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
--=_alternative 002D4A6780256E7E_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">We need to determine the list of components
and their owners for bugzilla CME reporting/tracking. &nbsp;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!)</font>
<br>
<br><font size=2 face="sans-serif">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.
&nbsp;So I was thinking of components like:</font>
<br>
<br><font size=2 face="sans-serif">Docs</font>
<br><font size=2 face="sans-serif">User Interface</font>
<br><font size=2 face="sans-serif">Composition</font>
<br><font size=2 face="sans-serif">Query</font>
<br>
<br><font size=2 face="sans-serif">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. &nbsp;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.</font>
<br>
<br><font size=2 face="sans-serif">Comments?</font>
<br>
<br><font size=2 face="sans-serif">Andy.</font>
<br>
<br><font size=2 face="sans-serif">===</font>
<br><font size=2 face="sans-serif">Andy Clement</font>
<br><font size=2 face="sans-serif">CME Development</font>
--=_alternative 002D4A6780256E7E_=--

--__--__--

Message: 2
To: cme-dev@xxxxxxxxxxx
Subject: Re: [cme-dev] Components/Owners for bugzilla?
From: Sian Whiting1 <SWHITING@xxxxxxxxxx>
Date: Thu, 22 Apr 2004 09:39:23 +0100
Reply-To: cme-dev@xxxxxxxxxxx

This is a multipart message in MIME format.
--=_alternative 002F66A580256E7E_=
Content-Type: text/plain; charset="US-ASCII"

That looks good - I'm happy to own the UI piece. What about a 'Concern Model' category for any problems people have in the Concern Explorer? Or 'Other' or a general 'Components' one for other bugs in the base?

Sian





Andrew Clement/UK/IBM@IBMGB Sent by: cme-dev-admin@xxxxxxxxxxx
22/04/2004 09:24
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

--=_alternative 002F66A580256E7E_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">That looks good - I'm happy to own the
UI piece. &nbsp;What about a 'Concern Model' category for any problems
people have in the Concern Explorer? &nbsp;Or 'Other' or a general 'Components'
one for other bugs in the base?</font>
<br>
<br><font size=2 face="sans-serif">Sian</font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Andrew Clement/UK/IBM@IBMGB</b>
</font>
<br><font size=1 face="sans-serif">Sent by: cme-dev-admin@xxxxxxxxxxx</font>
<p><font size=1 face="sans-serif">22/04/2004 09:24</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
cme-dev</font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">cme-dev@xxxxxxxxxxx</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">[cme-dev] Components/Owners
for bugzilla?</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2 face="sans-serif"><br>
We need to determine the list of components and their owners for bugzilla
CME reporting/tracking. &nbsp;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!)</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
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. &nbsp;So I was thinking of components
like:</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Docs</font><font size=3> </font><font size=2 face="sans-serif"><br>
User Interface</font><font size=3> </font><font size=2 face="sans-serif"><br>
Composition</font><font size=3> </font><font size=2 face="sans-serif"><br>
Query</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
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. &nbsp;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.</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Comments?</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Andy.</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
===</font><font size=3> </font><font size=2 face="sans-serif"><br>
Andy Clement</font><font size=3> </font><font size=2 face="sans-serif"><br>
CME Development</font>
<br>
--=_alternative 002F66A580256E7E_=--

--__--__--

Message: 3
Subject: Re: [cme-dev] Components/Owners for bugzilla?
To: cme-dev@xxxxxxxxxxx
From: Helen Hawkins <HAWKINSH@xxxxxxxxxx>
Date: Thu, 22 Apr 2004 09:56:35 +0100
Reply-To: cme-dev@xxxxxxxxxxx





That sounds a good place to start - we can see how it goes when bugs start
coming in - it might be that other areas become apparent once this gets
going. We also need to keep it easy for people to decide which component it
is that they're raising the bug against.

BTW - I'm happy to own the docs piece.

Helen


--__--__--

Message: 4
From: Matt Chapman <mchapman@xxxxxxxxxx>
Date: Thu, 22 Apr 2004 10:29:37 +0100
To: cme-dev@xxxxxxxxxxx
Subject: [cme-dev] Context sensitive menu actions for certain queries
Reply-To: cme-dev@xxxxxxxxxxx


We think it would be useful to be able to right-click on elements
and have options which generate certain queries, to save entering common
queries manually. See bug 59591 for more details:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=59591

We'd like to know if anyone has ideas for which sort of queries they'd
like to see supported in this way, in addition to the "Find implementors"
option mentioned in the bug. If you do, please either post here, or add
comments to the bug.

Elements are shown in the both the Search results view, and the Concern
Explorer, so I think the menu could appear on elements in both places.

Thanks,

Matt.



Back to the top