[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Re: [platform-releng-dev] Blocker/critical bug triage


Just to clarify. I am not asking to lower all severities; but rather to target severe issues properly.
As part of that effort, you may realize that some issues are no longer as severe as captured in the PR, if so then you may lower its priority (up to you).


__________________


In this case, I believe your issues are definitely no longer blocker/critical; and severity should be lowered accordingly; so the query will better reflect reality.
The severity reflects the reporter's perception, and it is still an important data point in our bug triage exercize (resulting sometimes into raising the priority for us in our plans).

All I am asking is that the query results better reflect reality, so we do not have to justify ourselves. Also, it may help categorize 3.4.1 work...



Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>  
Sent by: eclipse-dev-bounces@xxxxxxxxxxx

06/19/2008 02:47 PM
Please respond to
"General development mailing list of the Eclipse project."        <eclipse-dev@xxxxxxxxxxx>


To
"Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx>
cc
eclipse-dev@xxxxxxxxxxx, platform-releng-dev-bounces@xxxxxxxxxxx, platform-releng-dev@xxxxxxxxxxx
Subject
[eclipse-dev] Re: [platform-releng-dev] Blocker/critical bug triage






Philippe,

As much as I understand the need to keep an inbox free of "critical" bugs, the query does not produce an accurate picture.
For example this gathered many ancients bugs that have not been fixed for several releases (e.g in UM or PDE Build) and that we have no plan to fix. Maybe a more accurate query could involve the priority since this is supposed to the mechanism by which teams really triage things.

PaScaL

Philippe P Mulet ---06/19/2008 06:39:26 AM---Teams, I would like to see the remaining blocker/critical defects triaged before

From:

Philippe P Mulet <philippe_mulet@xxxxxxxxxx>

To:

platform-releng-dev@xxxxxxxxxxx, eclipse-dev@xxxxxxxxxxx

Date:

06/19/2008 06:39 AM

Subject:

[platform-releng-dev] Blocker/critical bug triage







Teams,

I would like to see the remaining blocker/critical defects triaged before end of June; so that we have a good guess of what 3.4.1 will look like.
Currently we have 65 with no target set:
https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Equinox&product=JDT&product=PDE&product=Platform&target_milestone=---&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&known_name=Eclipse-Critical&query_based_on=Eclipse-Critical&field0-0-0=noop&type0-0-0=noop&value0-0-0=

Please take the time now to assign proper milestones, or adjust the severities properly. I would hope that real blockers live no further than 3.4.1.

Thanks !

PS: Reports are cool...
https://bugs.eclipse.org/bugs/report.cgi?y_axis_field=product&cumulate=0&z_axis_field=&format=bar&x_axis_field=bug_severity&query_format=report-graph&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&target_milestone=---&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&action="">


Sauf indication contraire ci-dessus:/ Unless stated otherwise above:
Compagnie IBM France
Siège Social : Tour Descartes, 2, avenue Gambetta, La Défense 5, 92400 Courbevoie
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 542.737.118 euros
SIREN/SIRET : 552 118 465 02430
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev

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


Sauf indication contraire ci-dessus:/ Unless stated otherwise above:
Compagnie IBM France
Siège Social : Tour Descartes, 2, avenue Gambetta, La Défense 5, 92400 Courbevoie
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 542.737.118 euros
SIREN/SIRET : 552 118 465 02430


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



Sauf indication contraire ci-dessus:/ Unless stated otherwise above:
Compagnie IBM France
Siège Social : Tour Descartes, 2, avenue Gambetta, La Défense 5, 92400 Courbevoie
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 542.737.118 euros
SIREN/SIRET : 552 118 465 02430