[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [eclipse-dev] Planning Meeting Notes - Jun 7, 2006
|
JDT APT status:
- RC7 about.html fixes
- no other 3.2 fixes expected at this
time
- 3.3 planning
---------- Outreach ----------
Platform/JDT Text: -
finished German recipe editor article for inaugural English issue
of EclipseMagazine
(http://www.eclipsemag.net/) -------- Status
-------- Platform UI: - accessibility
testing - documentation and
screenshots - bug investigation
- bug 145310 [KeyBindings] keys
- investigated TreeViewer performance
bug (#140032, #144294) - talking about
improving the error dialog (#124964) -
internationalization JDT UI:
- RC 7 fixes: 2 fixes (1 doc fix) released
- documentation -
planing - inbox cleaning
Debug: - 3.2
documentation - 3.3 planning
Platform/JDT Text: -
no bug fixes for 3.2 RC7 - user and ISV doc
work and link checking - performance work for
next eclipse version: - instrumented
document to weight common usage scenarios - measured performance on common usage scenarios
- bugzilla inbox tracking - 1 public holiday JDT
Core: - 3 fixes for 3.2RC7
- 140879 Spontaneous error "java.util.Set cannot be
resolved..." - 144504 JDT Core model
JUnit tests fail when ordering of methods reversed - 143718 [1.6][compiler] ClassFormatError : wrong stack map
frame... - investigating more fixes for 3.2.1
maintenance SWT: - releasing fixes into 3.3 stream -
planning and prioritizing bigger items for 3.3 - starting Custom Draw Table/Tree article - ensuring that on-line content (eg.- older articles) is
up-to-date Workspace:
- Doc for 3.2 - Moving
Team/CVS web pages to new Eclipse web space/wiki
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.