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.
Difference between revisions of "Equinox Minutes - 20090331"
Line 22: | Line 22: | ||
*** The full Equinox SDK will be an aggregate of all the sub-project SDK features | *** The full Equinox SDK will be an aggregate of all the sub-project SDK features | ||
* Jetty | * Jetty | ||
+ | ** Moved to RT in Eclipse. | ||
+ | ** Interested in participating with Equinox for server-side stuff. | ||
+ | ** Not happening for Galileo. | ||
* Solaris x86 new platform? | * Solaris x86 new platform? |
Revision as of 14:52, 31 March 2009
Attendees
- DJ
- Simon
- Jeff
- Tom
- Andrew
- Pascal
- Matt
Agenda
- Log service has graduated. Where did we end up with API? It looks like org.eclipse.equinox.log is real API?
- Tom will review and open bugs accordingly. We decided to make this API.
- Simon will review since tags.
- Old Incubator. Starting to remove content from HEAD and placing readmes pointing to new repo for projects that moved.
- Need to release the map file before the nightly build; otherwise it will break tonight.
- Categorization in p2
- Target provisioning - making attractive targets for equinox runtime targets
- Equinox SDK will include all graduated stuff
- For target provisioning we will have one category for each sub-project (framework, components, compendium, server-side, security, p2, aspects?). That will require a new sdk feature for each sub-project.
- Jeff will create the new features for each SDK
- Someone in Ottawa will coordinate for building the new SDK features
- The full Equinox SDK will be an aggregate of all the sub-project SDK features
- Target provisioning - making attractive targets for equinox runtime targets
- Jetty
- Moved to RT in Eclipse.
- Interested in participating with Equinox for server-side stuff.
- Not happening for Galileo.
- Solaris x86 new platform?