Community
Participate
Working Groups
On the Eclipse platform we're about to face the deluge of bug reports that come when a new release is available. We expect most people will be downloading EPP packages, but most of those bugs will continue to be logged against the Eclipse platform component. It would be really useful for triage and investigation purposes to know which EPP package the bug occurred in. Is there any way we can incorporate this into the "enter bug" wizard that non-committers see when they enter bugs in our bugzilla? I'm not asking that we create new bugzilla products or components, but just that the wizard present a list of packages to the user and ask them to select one. That line could then be added automatically to the beginning of the description field. I'm thinking we would present a combo box with the same list of packages on the new download page: - Eclipse IDE for Java Developers - Eclipse IDE for Java EE Developers - Eclipse IDE for C/C++ Developers - Eclipse for RCP/Plug-in Developers - Classic Eclipse SDK - Other Eclipse distribution (please explain in description field)
John, now that the EPP packages have been available for some time, do you still think we need this?
We did see more bugs coming in after the release, but I am not sure if an additional combo box would help much. I would rather see time spent on bug 199802 because that could be a real time-saver for *every* committer. (Unless they are using Mylyn, I should add.)
Denis, I've polling around but there doesn't seem to be much interest. Feel free to mark as RESOLVED LATER ;)
(In reply to comment #3) > RESOLVED LATER ;) *shudder* *gasp* *cough*
Agree its a problem but not sure how much an EPP tag would help. The worst bucket we have is platform IDE which seems to be a dumping ground for "something bad happened somewhere in this massive packaging I am using". We end up triaging them although the majority aren't our bugs. Where an EPP tag could be helpful is if we had a component for it, and the different product teams took turns triaging. I can dream.
Fyi, it would be very easy to have Mylyn provide a customized New Bug Editor for bugs.eclipse.org (see bug 199802), and to have that custom editor provide buttons at the top that either set an existing attribute, or potentially automatically set a Product/Component. Or we could force people to do this by putting a page into the wizard that forces the user to select an EPP or Classic packaging, and then ask them where the problem originated (e.g. JEE Tools, Plug-in Development Tools, Java Tools, Mylyn, ...). Mylyn already retrieves the full repository configuration so all we would need is to include or retrieve the mapping from EPP bundling to Product. If someone would like to see this please file a bug against Mylyn.
That's an interesting suggestion Mik. Especially given than most of the packagings have Mylyn included. Could help a bit. We could embed the EPP package in description as John suggested or perhaps better use Whiteboard. I've entered request #205196 against Mylyn.
