I see three valuable ways:
1. Only report issues into the separate system and let committers review these items from time to time manually.
2. Report issues into the separate system and send daily reports to committers or project lists that there are new incoming problems.
3. Report issues into the separate system AND directly into the project’s bugzilla product/component.
Options 1. and 2. are on my todo list for M5. Your option 3 seems viable to me as well.
My proposal: Projects that wish to receive error reports directly in bugzilla, should say so (e.g. by a decision on the mailing list) and specify the bugzilla component to assign these reports with. I’ll add an UI for that.
What do you/others think?
thanks for the information.
From the platform.ui side I'm not sure that we will be able to adapt "yet another system" for looking at bug reports. IIRC the update of Bugzilla worked fine for us, with the only issue that the duplicate bug dedection has marking not the main bug and therefore created a long dependency chain. But I think this has been fixed.
Would it be possible to configure your intermediate system per comment to continue to create automatic Bugzilla entries? If yes, every project could vote to use your new system or continue to work only in Bugzilla.
Best regards, Lars
cross-project-issues-dev mailing listcross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940