Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Equinox/Plan/Galileo/Framework"

< Equinox‎ | Plan‎ | Galileo
(Framework)
Line 3: Line 3:
 
# Performance. Monitor overall performance and memory consumption which includes the addition of new performance tests for new features.
 
# Performance. Monitor overall performance and memory consumption which includes the addition of new performance tests for new features.
 
# Reliability. Provide APIs for clients where needed and fix critical bugs.
 
# Reliability. Provide APIs for clients where needed and fix critical bugs.
# Keep Eclipse vibrant and attractive.  Deliver new features specified in the next OSGi specification R4.2
+
# Keep Eclipse vibrant and attractive.  Deliver new features specified in the next OSGi specification R4.2.
 
# Testing.  Develop new tests to fill in gaps in the automated tests
 
# Testing.  Develop new tests to fill in gaps in the automated tests
 
=== OSGi R4.2 ===
 
=== OSGi R4.2 ===
Line 21: Line 21:
  
 
=== Current Milestone Plan: M3 - October 31, 2008 ===
 
=== Current Milestone Plan: M3 - October 31, 2008 ===
* Implement <nowiki>(RFC 138)</nowiki> - Tom, Erin
+
* [[Image:Progress.gif]] Implement <nowiki>(RFC 138)</nowiki> - Tom, Erin
* Implement <nowiki>(RFC 126)</nowiki> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=244625 Bug 244625]
+
* [[Image:Progress.gif]] Implement <nowiki>(RFC 126)</nowiki> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=244625 Bug 244625] - BJ
 +
* [[Image:Progress.gif]] Implement <nowiki>(RFC 132)</nowiki> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=244443 Bug 244443] - Tom
  
 
== Future Plans ==
 
== Future Plans ==
  
 
=== M4 - December 12th, 2008 ===
 
=== M4 - December 12th, 2008 ===
 
+
* [[Image:Glass.gif]] Focus on reliability, investigate thread safety issues - Tom, BJ
 +
* [[Image:Glass.gif]] Investigate improvements to the resolver algorithm for uses clause.
 
=== M5 - January 30th, 2009 - Major Feature Freeze ===
 
=== M5 - January 30th, 2009 - Major Feature Freeze ===
  
Line 49: Line 51:
 
=== M2 - September 19th, 2008 ===
 
=== M2 - September 19th, 2008 ===
  
* Planning
+
* [[Image:Progress.gif]] Planning
* Focus on 3.4.1 defects
+
* [[Image:Ok_green.gif]] Focus on 3.4.1 defects
* Port 3.4.1 fixes to 3.5 stream
+
* [[Image:Ok_green.gif]] Port 3.4.1 fixes to 3.5 stream
* Implement <nowiki>(RFC 120)</nowiki> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=242799 Bug 242799] - Tom
+
* [[Image:Ok_green.gif]] Implement <nowiki>(RFC 120)</nowiki> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=242799 Bug 242799] - Tom
* Started implementing <nowiki>(RFC 132)</nowiki> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=244443 Bug 244443] - Tom
+
* [[Image:Progress.gif]] Started implementing <nowiki>(RFC 132)</nowiki> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=244443 Bug 244443] - Tom
  
 
== Legend ==
 
== Legend ==

Revision as of 17:37, 10 September 2008

Framework

Overall Goals

  1. Performance. Monitor overall performance and memory consumption which includes the addition of new performance tests for new features.
  2. Reliability. Provide APIs for clients where needed and fix critical bugs.
  3. Keep Eclipse vibrant and attractive. Deliver new features specified in the next OSGi specification R4.2.
  4. Testing. Develop new tests to fill in gaps in the automated tests

OSGi R4.2

  • Updates to Conditional Permission Admin service (RFC 120) Bug 242799 - IBM
  • Service Registry Hooks (RFC 126) Bug 244625 - IBM
  • SystemBundle (Framework) booting (RFC 132) Bug 244443 - IBM
  • Support for peer and child frameworks running in the same VM. (RFC 138, still very early) - IBM

Performance and Size

  • Investigate places where we can rid the framework of bulky and unnecessary abstraction layers to reduce size and improve performance (service registry abstraction, resolver abstraction etc.).
  • Make "uses" clause usable for large installs.

Reliability

  • Review and fix thread safety issues in the Framework Bug 245251 - IBM

Milestones

Current Milestone Plan: M3 - October 31, 2008

  • Progress.gif Implement (RFC 138) - Tom, Erin
  • Progress.gif Implement (RFC 126) Bug 244625 - BJ
  • Progress.gif Implement (RFC 132) Bug 244443 - Tom

Future Plans

M4 - December 12th, 2008

  • Glass.gif Focus on reliability, investigate thread safety issues - Tom, BJ
  • Glass.gif Investigate improvements to the resolver algorithm for uses clause.

M5 - January 30th, 2009 - Major Feature Freeze

M6 - March 12th, 2009 - API Freeze

  • Polish API javadoc, package.html doc

M7 - May 1st, 2009 - Development Complete

  • Polish items
  • Performance work
  • Testing and test framework improvements

Previous Plans

M1 - August 8th, 2008

  • Bug triage
  • Fixing critical defects

M2 - September 19th, 2008

  • Progress.gif Planning
  • Ok green.gif Focus on 3.4.1 defects
  • Ok green.gif Port 3.4.1 fixes to 3.5 stream
  • Ok green.gif Implement (RFC 120) Bug 242799 - Tom
  • Progress.gif Started implementing (RFC 132) Bug 244443 - Tom

Legend

Glass.gif Needs some investigation

Progress.gif Patch in progress

Ok green.gif Bug fixed / Feature added

Back to the top