Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-ui-dev] Problem Digest for Project Eclipse Platform

Dear platform-ui-dev,

you just received the first daily digests for normal problems & UI freezes. I’d like to share a few general details about these digests.


1. Problems listed on these digests require a minimum number of (5) distinct users.
This setting is stored in your project configuration [1] and can be edited any time by yourself.

1a. All problems on this daily digest have been reported by at least one user in the last 24 hours.
In case you wonder why there are some problems with 23 reporters and others with just 5 reporters.

2. These problems will only appear once on this digest.
We keep track which alert was triggered per problem and don’t trigger it twice. Thus, please inspect the issue as soon as it appears on this list and take appropriate action. 

3. How/which actions to take.
An action may be (i) creating a bug or (ii) marking the issue as log message. Both can be done from the linked triage page (see [2] for an example).
You may also ignore it and postpone any action indefinitely.  If you decide to ignore it, please keep in mind that it won’t appear on future digest lists. But you may define a second alert with threshold of, say, 50 to get that reminder.

4. Who can read these reports.
The web ui is requires committer status. If you want non-eclipse users to comment on your issue (e.g you need further information), you have to create a bug from the report. As soon as there is a bug linked with an error report, new reporters will get notified about this bug and may join the discussion on your bug.

5. How to request further information.
If a problem is linked to an open bugzilla ticket, all users reporting a trace that was matched to this problem, will receive a notification that there is a bug and that it needs their help. it would be helpful if you could specify which information you need in a bug comment.

A more direct way to tell a user what information you are looking is to set the needinfo keyword in the bug report and specify your request message in the bug’s whiteboard field. This message is then send to the user as soon as he hits that issue.


If you have an further questions, don’t hesitate to ask me.
If you have suggestions how to improve the system, please let me know.
If something is, say, underwhelming, drop me a few lines.
There is also a guide that may help answering a fee questions [3].

Best regards,
Marcel

P.S.: The list of problems may be longer than usual in the beginning since the alert is catching up with all issues that have been reported before. The number of items on this list is expected to go down to 5 per day as soon as tailback was send to the list.



Back to the top