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 "Libra/Status Meetings/2011-02-23"
< Libra | Status Meetings
m |
|||
| Line 21: | Line 21: | ||
:EclipseSource completed the contribution process for the WAR Products feature. IP process is completed: [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=4837 CQ 4837]. Source code is in the Git repository. | :EclipseSource completed the contribution process for the WAR Products feature. IP process is completed: [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=4837 CQ 4837]. Source code is in the Git repository. | ||
| + | |||
:SAP completed the contribution process for the OSGi Bundle Facet feature. IP process is completed: [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=4844 CQ 4844]. Source code is in the Git repository. | :SAP completed the contribution process for the OSGi Bundle Facet feature. IP process is completed: [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=4844 CQ 4844]. Source code is in the Git repository. | ||
| + | |||
:IBM contribution is attached to Bugzilla ([https://bugs.eclipse.org/337575 337575]) and about to start the IP process - immediately after Zina completes the committer provisioning process. However, the feature contributed will not be delivered as part of Indigo. | :IBM contribution is attached to Bugzilla ([https://bugs.eclipse.org/337575 337575]) and about to start the IP process - immediately after Zina completes the committer provisioning process. However, the feature contributed will not be delivered as part of Indigo. | ||
| + | |||
:Eteration contribution has been attached to Bugzilla ([https://bugs.eclipse.org/330491 330491]) for a long time. The Eteration committers are currently refactoring the code and they will soon (end of this week) start the IP process. However, the feature contributed will not be delivered as part of Indigo. | :Eteration contribution has been attached to Bugzilla ([https://bugs.eclipse.org/330491 330491]) for a long time. The Eteration committers are currently refactoring the code and they will soon (end of this week) start the IP process. However, the feature contributed will not be delivered as part of Indigo. | ||
| + | |||
:VMWare/SpringSource committers do not plan any contributions in the Libra project for the next months. They are about to start the IP process for contributing the Virgo Tools in a subproject under the Eclipse Runtime top-level project. The next step will be to refactor the generic parts, that are not specific to Virgo, and move them to the Libra project. | :VMWare/SpringSource committers do not plan any contributions in the Libra project for the next months. They are about to start the IP process for contributing the Virgo Tools in a subproject under the Eclipse Runtime top-level project. The next step will be to refactor the generic parts, that are not specific to Virgo, and move them to the Libra project. | ||
| + | |||
:No other contributions planned so far. | :No other contributions planned so far. | ||
| − | + | ;Indigo release train | |
| − | + | ||
| − | + | :EclipseSource and SAP requests that Libra joins the Indigo Simultaneous Release. None of the other committers requests the Libra joins Indigo, but none of them does not object this too. | |
| + | |||
| + | :We need to meet some of the [http://eclipse.org/indigo/planning/EclipseSimultaneousRelease.php requirements] of the Simultaneous Release Train by M6: | ||
*** Planning (M4) | *** Planning (M4) | ||
*** IP Logs (M5-M7) | *** IP Logs (M5-M7) | ||
*** Support translations - externalize strings, register in the Babel project (M6) | *** Support translations - externalize strings, register in the Babel project (M6) | ||
*** Ramp Down Planned and Defined (M6) | *** Ramp Down Planned and Defined (M6) | ||
| + | |||
** Releases | ** Releases | ||
*** Shall we have official releases before Indigo? | *** Shall we have official releases before Indigo? | ||
*** What will be the version of our Indigo release? 0.1, 0.5, 1.0? | *** What will be the version of our Indigo release? 0.1, 0.5, 1.0? | ||
Revision as of 05:48, 24 February 2011
Attendees
- Kaloyan Raev
- Holger Staudacher
- Martin Lippert
- Zina Mostafia
- Naci Dai
- Ani Koycheva
Meeting Minutes
- Project provisioning
- The Libra project has already been provisioned. We have a Git repository and a Hudson build already running. The SAP committers are currently working on the content of the project's web site.
- Committer's provisioning
- It looks like most of the committers went successfully through the committer provisioning process. Only the process for Zina is not completely finished. The status in the Portal is "Waiting for candidate paperwork. Received NCRF". Kaloyan and Zina will check with EMO.
- Initial contributions
- EclipseSource completed the contribution process for the WAR Products feature. IP process is completed: CQ 4837. Source code is in the Git repository.
- SAP completed the contribution process for the OSGi Bundle Facet feature. IP process is completed: CQ 4844. Source code is in the Git repository.
- IBM contribution is attached to Bugzilla (337575) and about to start the IP process - immediately after Zina completes the committer provisioning process. However, the feature contributed will not be delivered as part of Indigo.
- Eteration contribution has been attached to Bugzilla (330491) for a long time. The Eteration committers are currently refactoring the code and they will soon (end of this week) start the IP process. However, the feature contributed will not be delivered as part of Indigo.
- VMWare/SpringSource committers do not plan any contributions in the Libra project for the next months. They are about to start the IP process for contributing the Virgo Tools in a subproject under the Eclipse Runtime top-level project. The next step will be to refactor the generic parts, that are not specific to Virgo, and move them to the Libra project.
- No other contributions planned so far.
- Indigo release train
- EclipseSource and SAP requests that Libra joins the Indigo Simultaneous Release. None of the other committers requests the Libra joins Indigo, but none of them does not object this too.
- We need to meet some of the requirements of the Simultaneous Release Train by M6:
- Planning (M4)
- IP Logs (M5-M7)
- Support translations - externalize strings, register in the Babel project (M6)
- Ramp Down Planned and Defined (M6)
- Releases
- Shall we have official releases before Indigo?
- What will be the version of our Indigo release? 0.1, 0.5, 1.0?
- Releases