RE: [eclipse.org-requirements-council] Mapping of Eclipse Themes toBugs

["Paul Clenahan" <pclenahan@xxxxxxxxxxx>]

It makes sense to give them the option. They would do this by adding dependants to the "theme" bugs. 

I am not sure how many will add a lot here though, or whether we would want every bug associated with a theme added. For example, in the BIRT 2.1 plan we made an effort to associate every plan entry with a theme. If we associated all those items with the Bugzilla entry for the theme then be harder to see the more core issues.

As an additional note, I will add a link to the Bugzilla query for each theme in the Wiki. 

Paul.


-----Original Message-----
From: "Gupta, Anurag SEA" <anurag.sea.gupta@xxxxxxxxx>
To: "eclipse.org-requirements-council" <eclipse.org-requirements-council@xxxxxxxxxxx>
Sent: 6/28/06 12:44
Subject: RE: [eclipse.org-requirements-council] Mapping of Eclipse Themes toBugs

The approach that Paul suggests makes sense. Does it make sense to ask
the AC and PC to identify bugzilla entries that support the themes
written on wiki?

 

Thanks

Anurag

 

________________________________

From: eclipse.org-requirements-council-bounces@xxxxxxxxxxx
[mailto:eclipse.org-requirements-council-bounces@xxxxxxxxxxx] On Behalf
Of Paul Clenahan
Sent: Wednesday, June 28, 2006 9:02 AM
To: eclipse.org-requirements-council
Subject: [eclipse.org-requirements-council] Mapping of Eclipse Themes to
Bugs

 

Requirements Council,

 

Here is the email from Mike a while back on the mechanism to track
Bugzilla entries that relate to a particular Theme. The idea was to cc
each of the email addresses below on any bugzilla entries of entries.

 

This has not been implemented (at least there are no Bugzilla entries
with these cc's), so I don't think we are locked into this approach.

 

I liked the idea from Ed at the Plenary today. Using "Depends On" seems
like a better way to track this. Then dependency trees can be used to
easily see what Bugzilla entries are attached to a particular theme.

 

If we agree on this approach, I think the next steps would be:

 

1. Create a Bugzilla entry for each top level Theme (Paul C can do this)

2. Assign the Bugzilla entries to
eclipse.org-requirements-council@xxxxxxxxxxx (Paul C can do this)

3. Add links to the Bugzilla entries to Wiki page beside each theme
(Paul C can do this)

4. Associate related Bugzilla entries to each Theme Bugzilla entry
(Requirements Council)

 

Do we agree that this makes sense? If so, I will do the first steps.

 

Paul.

 

________________________________

From: eclipse.org-requirements-council-bounces@xxxxxxxxxxx
[mailto:eclipse.org-requirements-council-bounces@xxxxxxxxxxx] On Behalf
Of Mike Milinkovich
Sent: Sunday, November 27, 2005 1:39 PM
To: 'eclipse.org-requirements-council'
Subject: [eclipse.org-requirements-council] Mapping of Themes to Bugs

All,

 

First off, please review and comment on the attached spreadsheet. I
believe I have now captured all of the outstanding requirements that
everyone has provided. Unfortunately, my searches of Bugzilla have not
been able to find bugs for every one of the items.

 

So here are the names for the mailing lists that I am going to have set
up:

	rc_broader_community_theme
	rc_extensibility_theme
	rc_embedded_theme
	rc_multi-language_theme
	rc_enterprise_ready_theme
	rc_rcp_theme
	rc_scaling_up _theme
	rc_simple_to_use_theme

Each of these lists and their digests will be publicly accessible.

 

Mike Milinkovich
Executive Director,
Eclipse Foundation, Inc.
Office: 613-224-9461 x228
Cell: 613-220-3223
mike.milinkovich@xxxxxxxxxxx

 

blog: http://milinkovich.blogspot.com/