Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipse-dev] Planning Meeting Notes - Nov 10, 2004 
------------------- 
 Discussion Topics
------------------- 

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

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


Debug:
- console performance improvements when flooded with hyperlinks
- persistence of 'stack trace console' contents
- started work on console example for Eclispe Corner article
- fixes to deadlock detection updating and for VMs that don't support
  monitor information retrieval
- added JUnit tests for 'run to line'
- M3 Test/Fix Pass
- post M3 bug fixing

Ant:
- added an SWT based input handler for seperate VM builds 
  - also posted as a downloadable patch for use in 3.0.1(see 
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-ant-home/main.html)
- added performance tests
- profiled for memory leaks
- M3 Test/Fix Pass
- post M3 bug fixing


Rel. Eng.:
- adding support to source builds to compile eclipse executable and swt
  native libraries for HPUX Motif IA64, Linux GTK ppc/ppc64
- improving performance result presentation
- adding performance testing on Linux GTK 
- setting up new performance server
- preparation to run performance tests on previous eclipse releases and
  milestones.
- 3.1 M3 builds
- move to using 3.1M3 plug-ins in eclipse 3.1 stream builds

Platform/JDT Text:
- shipped 3.1 M3
- M4 planning:
  - initial version of M4 plan is available
- comment formatter migration: submitted first set of patches to JDT/Core)
- backported performance tests to 2.1.2, 3.0 and 3.0.1
- worked with the Platform UI team on preferences rework
- continued working with the WTP team on a better integration with the
  Eclipse
- continued work on nls tooling
- investigate bug 77204: [implementation] Cannot save CU due to wrong
  IBuffer in BufferCache
- bug fixing

Performance plug-in:
- addition to performance testing framework (add NullPerformanceMeter to
  test.performance)
- update of Performance HowTo (add section about running tests from the
  command-line)
- work on stabilizing performance tests:
  - suggested to make -Xms256M -Xmx256M the default for performance
    measurements;
  - should not require action from teams other than Releng


JDT/UI:
- M3 milestone (test / fix pass)
- planning M4
- bug fixing
- contributed to preferences dynamic team
- J2SE 5.0 theme
  - added support to generate delegate and deprecate it for moved 
    instance method (instead of removing it).
  - investigated impact of static imports on refactorings
  - added support to handle overridden method to augment raw container
    clients.
- Refactoring
  - worked on more visibility adjustment support for move 
    refactorings (e.g move type, move static member, ...)

Platform/Search:
- implemented first set of search tests

Platform/Compare:
- bug fixing

Mac OS X:
- tracked down a problem with headless AWT running inside SWT application

Performance plug-in:
- bug fixing
- added support for "Derby", Apache's OS version of cloudscape.

JDT/Core:
- M3 milestone (test / fix pass)
- M4 plan posted at
 
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-core-home/r3.1/main.html#milestone-plan
- tuned support for generics
- tuned DOM binding keys
- ICompletionRequestor was deprecated. Use CompletionRequestor instead
- bug fixing

PDE:
- M4 planning
- Bug fixes

Install/Update:
- M4 plan posted
- Reviewing support for digital signatures and prompts for accepting
  unsigned features
- Integrating patches contributed by CDC Foundation
- Bug fixes

Help/Intro:
- Continued work on the User Assistance strategy
- Started work on the support required by RedHat (to facilitate
  os-specific images and documents)

Platform Core:
- registry structure code review 
- more work on replacing the indexed store: numbers are looking better
- information gathering on resource bundle problems
- preferences dynamic team (see UI dynamic team page for details)
- M4 planning
- bug triage

Platform UI: 
- bug fixing
- work on component framework ( 
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-ui-home/services-proposal/ServiceFrameworkProposal.html 
)
- cross team work:
  - Preferences dynamic team ( 
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-ui-home/R3_1/dynamic_teams/dynamic_teams.html#team1 
)
  - Action Contributions
    - this will be updated as soon as the information is available ( 
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-ui-home/R3_1/dynamic_teams/dynamic_teams.html#team2 
)
- planning a second instrumentation survey with more detailed results
- backported performance tests to older branches

Back to the top