Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » General (non-technical) » Eclipse Foundation » Callisto bugzilla inbox
Callisto bugzilla inbox [message #33852] Thu, 27 April 2006 09:56 Go to next message
Olivier Thomann is currently offline Olivier Thomann
Messages: 518
Registered: July 2009
Senior Member
Hi,

I tested Callisto yesterday and I have to admit that it is not trivial
to guess against what component we should report bugs.
For example, there is a XDoclet preference page.
But when you open it, you get a popup saying that xdoclet-1.2.1.jar is
missing. I'd like to report this error, but I have no idea what
component defines this preference page.
It would be nice to have an inbox where we could open bug reports and
components involved in Callisto could check it to find out if bugs
related to their component having been entered.

Any comment?

Olivier
Re: Callisto bugzilla inbox [message #34006 is a reply to message #33852] Thu, 27 April 2006 12:01 Go to previous messageGo to next message
Eclipse User
Originally posted by: john.eclipsefaq.org

I agree with this problem. I spent quite a lot of time trying to find
the owner of the generic "Data" and "Analysis" preference pages in order
to report bugs. There is no single person who would be able to perform
this triage, but I can't imagine how people in the greater community
would go about trying to figure out what component to log Calisto bugs
in (some people find it hard enough with just the Eclipse SDK). I think
it may be worth trying Olivier's suggestion of a single triage area that
someone from each project could monitor for triage. Anyone have other
suggestions about how/where the community can enter Callisto bugs when
there is no obvious matching component?
--

Olivier Thomann wrote:
> Hi,
>
> I tested Callisto yesterday and I have to admit that it is not trivial
> to guess against what component we should report bugs.
> For example, there is a XDoclet preference page.
> But when you open it, you get a popup saying that xdoclet-1.2.1.jar is
> missing. I'd like to report this error, but I have no idea what
> component defines this preference page.
> It would be nice to have an inbox where we could open bug reports and
> components involved in Callisto could check it to find out if bugs
> related to their component having been entered.
>
> Any comment?
>
> Olivier
Re: Callisto bugzilla inbox [message #34017 is a reply to message #34006] Thu, 27 April 2006 13:25 Go to previous messageGo to next message
Randy D. Smith is currently offline Randy D. Smith
Messages: 394
Registered: July 2009
Senior Member
John Arthorne wrote:
> I agree with this problem. I spent quite a lot of time trying to find
> the owner of the generic "Data" and "Analysis" preference pages in order
> to report bugs. There is no single person who would be able to perform
> this triage, but I can't imagine how people in the greater community
> would go about trying to figure out what component to log Calisto bugs
> in (some people find it hard enough with just the Eclipse SDK). I think
> it may be worth trying Olivier's suggestion of a single triage area that
> someone from each project could monitor for triage. Anyone have other
> suggestions about how/where the community can enter Callisto bugs when
> there is no obvious matching component?
> --
>
> Olivier Thomann wrote:
>
>> Hi,
>>
>> I tested Callisto yesterday and I have to admit that it is not trivial
>> to guess against what component we should report bugs.
>> For example, there is a XDoclet preference page.
>> But when you open it, you get a popup saying that xdoclet-1.2.1.jar is
>> missing. I'd like to report this error, but I have no idea what
>> component defines this preference page.
>> It would be nice to have an inbox where we could open bug reports and
>> components involved in Callisto could check it to find out if bugs
>> related to their component having been entered.
>>
>> Any comment?
>>
>> Olivier

For bugs, there's a Callisto Component under the Eclipse Foundation
Community "Product". For reaching across projects for triaging when you
don't know where to go, you might ping the cross-projects mailing list
(< https://dev.eclipse.org/mailman/listinfo/cross-project-issue s-dev >).

As to the specific prolbems you chased, Analysis appears to be TPTP's
Platform.Analysis Component. I don't know about Data though.


--
RDS

Randy D. Smith randy (dot) d (dot) smith (at) intel (dot) com
Eclipse TPTP Committer, Platform Proj (data collection/agent controller)
Re: Callisto bugzilla inbox [message #34034 is a reply to message #34017] Thu, 27 April 2006 16:36 Go to previous message
Eclipse User
Originally posted by: john.eclipsefaq.org

Randy D. Smith wrote:
> For bugs, there's a Callisto Component under the Eclipse Foundation
> Community "Product". For reaching across projects for triaging when you
> don't know where to go, you might ping the cross-projects mailing list
> (< https://dev.eclipse.org/mailman/listinfo/cross-project-issue s-dev >).
>
> As to the specific prolbems you chased, Analysis appears to be TPTP's
> Platform.Analysis Component. I don't know about Data though.
>

Thanks. It turned out "Data" comes from Web tools (I would have thought
data tools). I'll use the Callisto component in the future if I can't
find the originator then.
--
Previous Topic:Sponsored Committers?
Next Topic:So... who actually uses Eclipse???
Goto Forum:
  


Current Time: Wed Jul 30 11:23:31 EDT 2014

Powered by FUDForum. Page generated in 0.01557 seconds