Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Your friendly error reports bot is suspended
Do I = e(fx)clipse have to opt-in explictly if i want to go with option 2?

Tom

Von meinem iPhone gesendet

Am 09.01.2015 um 08:04 schrieb Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx>:

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?

Best,
Marcel

On 09 Jan 2015, at 05:04, Lars Vogel <lars.vogel@xxxxxxxxx> wrote:

Hi Marcel,

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

2015-01-08 8:55 GMT+01:00 Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx>:
Hi Lars,

no, there is no bug for this. But an interim system is live and receives errors. 

The UI also offers basic search capabilities now. See [1] for an overview and [2] for an example of a concrete query. It also offers a set of predefined per-project queries (see below for a comprehensive list).


Plans are to have it operational by M5 (end of January). Until M5 the proposed workflow is as follows:

1. Committers can review the 'project problem listings' (given below) once per day
2. For every new problem that (you think) needs a closer look, move it to Bugzilla. Convenient support for this will be added tomorrow.


Some notes about the interim system:
1. Even if possible, please do not make any changes in ui except creating bugs from there; they might get lost during system updates.
2. Bugzilla is the only stable reference you have. Thus, move errors to Eclipse’ Bugzilla if you think they are bugs and start working on them there.
3. Once a bug was created in bugzilla, don’t look back or try to keep the error reporting system in-sync. Eventually we’ll do that automatically.
4. Problem statistics and duplicate detection results may look suspicious at times. It's more challenging than it may look on a first sight to detect duplicates in large, moving code bases. 

Having said this, I’m happy to receive feature requests and suggestions by email (probably better off this list) or, preferably, via bugzilla.

Best,
Marcel


Unconfirmed problems by project Quickstarter Queries








On 07 Jan 2015, at 11:30, Lars Vogel <lars.vogel@xxxxxxxxx> wrote:

Hi Marcel,
> I’ve been asked to shutdown the collector to keep the annoyance low until this is fixed, which I do hereby.

Do you have the bug number for the pending fix in the error reporting bot?

Best regards, Lars 

2014-12-19 7:35 GMT+01:00 Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx>:
Hi,

in Bug 455361 Konstantin expressed his annoyance about another comment  on his bug.
I’ve been asked to shutdown the collector to keep the annoyance low until this is fixed, which I do hereby.

The collector will continue to receive errors but will not send notifications to anyone or create comments in bugzilla.


Happy Christmas Season
Marcel
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

-- 
Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

-- 
Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-179-131-7721
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Back to the top