Re: [eclipse-dev] Planning Meeting Notes - Feb 23, 2005

[Michael Van Meekeren <Michael_Van_Meekeren@xxxxxxxxxx>]

Platform UI:
- Last minute EclipseCon preparation
- M5 testing/fixing
- copyright related work
- 3.0.2 fixes

Mike Wilson/Ottawa/IBM@IBMCA
Sent by: eclipse-dev-admin@xxxxxxxxxxx

02/22/2005 02:46 PM

Please respond to
eclipse-dev

To	eclipse-dev@xxxxxxxxxxx
cc
Subject	[eclipse-dev] Planning Meeting Notes - Feb 23, 2005

------------------- 
 Discussion Topics
------------------- 

JDT Core:
- How much unicode-4 support are we planning for 3.1 ? 
  - Java5.0 supports it. 
  - The Java compiler now properly handles them (using some its own
    implementation to be able to cross-compile).

---------- 
 Outreach 
---------- 

-------- 
 Status
--------

Debug:
- M5 testing/fixing
- EclipseCon prep
- attended VTP (Voice Tools Project) and PTP (Parallel Tools Platform)
  Creation Review meetings

Ant:
- M5 testing/fixing
- SDWest preparation
- submitted proposals to OSCON

Platform/JDT Text:
- shipping 3.1 M5
- EclipseCon preparation
- Performance: 
  - fixed and backported performance tests using Display.post(Event)
  - still trying to find out with Releng why Linux fingerprints are
not
    available for JDT Text tests
- started to investigate performance degradation and StackOverflows in
  our correctness tests
- started 3.1 M6 planning
- bug fixing
- bug inbox tracking

JDT UI:
- M5 testing/fixing
- planning M6
- theme J2SE 5.0:
  - made extract constant J2SE 5.0 aware
  - finished cleanup of type constraint infrastructure for extract
    interface and use supertype. Now uses compiler loop, new
less
    memory intensive type constrain infrastructure and generates
    less number of constraints.
- EclipseCon preparation

JDT Core:
- M5 delivery
- bug fixing
- M6 planning
- separated inclusion/exclusion filters from import restrictions on
  IClasspathEntry
- classpath entries can be annotated with attributes (e.g. javadoc
  location), see JavaCore#newClasspathAttribute
- added optional compiler diagnosis to detect type parameter colliding
  with another type
- added optional compiler diagnosis to signal usage of an annotation
  type as superinterface
- #isInterface() predicates (java element and DOM AST) are now answering
  true for annotation types (since these can be implemented as well)
- EclipseCon material preparation

Rel. Eng.:
- M5
- EclipseCon poster prep
- build mechanism and source build script testing
- copyright tool modification for CPL to EPL
- run performance tests for 3.1M5a:
 
(http://download.eclipse.org/downloads/drops/S-3.1M5a-200502191500/performance/performance.php)

Platform Core:
- content type work
- running from JARs (work in Runtime and PDE/Build)
- performance infrastructure
- updated copyrights to EPL
- bug fixing
- M5 work
- M6 planning
- EclipseCon preparation

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