Re: [cross-project-issues-dev] Removing non related projects when triaging AERI issues
|Thanks Alexander, makes sense. Can you please create a bug we can use to track this request?|
FWIW, we have extra logic in place for projects like Xtext (which is used by OCL, Papyrus and others) when one of their clients is on the stack, we’ll remove xtext from the list of projects. We could do the same for GEF.
If we should do the same for GEF, please also create a bug report and list the projects we should use for removal checks.
Because GEF is contained in pretty much all the stack traces of its adopters (GMF, Sirius, Papyrus and others) I find myself triaging several issues that are actually not related to problems in GEF. That’s fine, I don’t want to lament that GEF has a lot of adopters and of course I want to support them all. However, I recently ran into cases were issues were indeed already triaged (i.e. a bugzilla was created for a specific project), but the list of projects was not adjusted. In order to reduce overhead, it would IMHO be a good policy to remove other projects from an AERI issue in case triaging leads to a bugzilla for a specific project (the projects list can easily be edited during triaging, and non-related projects can simply be removed from it).
Dr. Alexander Nyßen
Telefon: +49 (0) 231 / 98 60-202
Telefax: +49 (0) 231 / 98 60-211
Mobil: +49 (0) 151 / 17396743http://www.itemis.de alexander.nyssen@xxxxxxxxx
Am Brambusch 15-24
Amtsgericht Dortmund, HRB 20621
Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens Trompeter, Sebastian Neus
Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer Fiorentino
cross-project-issues-dev mailing listcross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
Description: Message signed with OpenPGP using GPGMail