[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse-dev] Architecture meeting notes
|
>. I think that going back and assessing these bugs is a good idea, after
we have established a way forward.
You mean teams should not go and asses them now? I see that some bugs need
investigation upfront but others just need to be fixed.
Dani
Steve Northover
<Steve_Northover@
ca.ibm.com> To
Sent by: "General development mailing list
eclipse-dev-bounc of the Eclipse project."
es@xxxxxxxxxxx <eclipse-dev@xxxxxxxxxxx>
cc
eclipse-dev@xxxxxxxxxxx,
13.12.2007 18:28 eclipse-dev-bounces@xxxxxxxxxxx
Subject
Re: [eclipse-dev] Architecture
Please respond to meeting notes
"General
development
mailing list of
the Eclipse
project."
<eclipse-dev@ecli
pse.org>
There are 2 types of leaks: object leaks and operating system resource
leaks. I think that going back and assessing these bugs is a good idea,
after we have established a way forward.
I suggest we start with this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=212345
Philippe P Mulet <philippe_mulet@xxxxxxxxxx>
Sent by: eclipse-dev-bounces@xxxxxxxxxxx
To
eclipse-dev@ecli
12/13/2007 10:13 AM pse.org
cc
Please respond to Subject
"General development mailing list of the Re:
Eclipse project." [eclipse-dev]
<eclipse-dev@xxxxxxxxxxx> Architecture
meeting notes
As Dani observed, we are already aware of existing leaks...
I would like to see these bugs assessed and targeted for 3.4M5. Severe leak
fixes could be considered for 3.3.2 as well maybe...
https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=Eclipse&email1=&email2=&emailtype1=substring&emailtype2=substring&field-1-0-0=classification&field-1-1-0=bug_status&field-1-2-0=short_desc&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&query_format=advanced&remaction=&short_desc=leak&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type-1-2-0=allwordssubstr&type0-0-0=noop&value-1-0-0=Eclipse&value-1-1-0=UNCONFIRMED,NEW,ASSIGNED,REOPENED&value-1-2-0=leak&value0-0-0=&votes=&order=bugs.bug_severity,bugs.priority,bugs.bug_severity,bugs.priority,bugs.target_milestone,bugs.bug_id&query_based_on=
Tod Creasey <Tod_Creasey@xxxxxxxxxx>
Sent by: eclipse-dev-bounces@xxxxxxxxxxx
To
12/12/2007 17:44 eclipse-dev@ecl
ipse.org
cc
Please respond to
"General development mailing list of the Subject
Eclipse project." [eclipse-dev]
<eclipse-dev@xxxxxxxxxxx> Architecture
meeting notes
Forming a performance dynamic team to decide on a way to detect resource
and memory leaks. Teams are requested to provide a representative.
_______________________________________________
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:
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 €
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
_______________________________________________
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
