Jump to: navigation, search

Difference between revisions of "Equinox/Plan/Galileo"

< Equinox‎ | Plan
(OSGi R4.2)
 
(7 intermediate revisions by 4 users not shown)
Line 2: Line 2:
  
 
== Framework ==
 
== Framework ==
=== OSGi R4.2 ===
+
See [[Equinox/Plan/Galileo/Framework | Framework Galileo plan]].
* Updates to Conditional Permission Admin service <nowiki>(RFC 120)</nowiki>
+
* Service Registry Hooks (RFC 126)
+
* SystemBundle (Framework) booting (RFC 132)
+
* Improve Equinox support for peer and child frameworks running in the same VM.  (RFC 138, still very early)
+
 
+
=== 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.
+
  
 
== p2 ==
 
== p2 ==
See the [[Equinox p2 3.5 contributions|p2 planning page]]
+
See [[Equinox/p2/Galileo/Features | p2 Galileo Proposed Features]] and [[Equinox/p2/Plan | p2 Milestone Plan]].
  
 
== Compendium and Components==
 
== Compendium and Components==
 
=== Registry ===
 
=== Registry ===
* need for the registry to support multiple locales and locale switching [http://code9.com Code 9]
+
* Support multiple locales and locale switching in the registry [http://code9.com Code 9]
 +
* Explore future direction of the registry, such as creating user-defined objects instead of generic configuration elements, and adding support for non-singleton bundles [IBM]
  
 
== Server-side==
 
== Server-side==
Line 23: Line 16:
  
 
== Security ==
 
== Security ==
 +
 +
See the [http://wiki.eclipse.org/Equinox/Plan/Galileo/Security Galileo Security Plan]
 +
 +
[[Category:Equinox]]

Latest revision as of 13:10, 16 June 2009

Equinox Galileo planning. Teams and community members should add work items and work areas to the pages here as input to the Galileo planning process. Note that this is intended to gather input for work that people are planning to contribute, not just things that people would like to see done. Putting your name beside something does not imply that you will do the whole task but does imply that you will put non-trivial effort into it. Items with no names beside them generally do not make it on to the final plan nor do they get done.

Framework

See Framework Galileo plan.

p2

See p2 Galileo Proposed Features and p2 Milestone Plan.

Compendium and Components

Registry

  • Support multiple locales and locale switching in the registry Code 9
  • Explore future direction of the registry, such as creating user-defined objects instead of generic configuration elements, and adding support for non-singleton bundles [IBM]

Server-side

  • Session and user support Code 9

Security

See the Galileo Security Plan