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
| (4 intermediate revisions by the same user not shown) | |||
| Line 34: | Line 34: | ||
;Indigo release train | ;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. | + | :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. Kaloyan will trigger the process with the Eclipse Planning Council. |
| − | :We need to meet some of the [http://eclipse.org/indigo/planning/EclipseSimultaneousRelease.php requirements] of the Simultaneous Release Train by M6 | + | :We need to meet some of the [http://eclipse.org/indigo/planning/EclipseSimultaneousRelease.php requirements] of the Simultaneous Release Train by M6. EclipseSource and SAP committers will take the necessary actions to ensure that Libra will meet the requirements on time. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | ** | + | ::* Planning (M4) |
| − | *** | + | ::*: We need to provide a project plan for Indigo: bug [https://bugs.eclipse.org/338129 338129] (Kaloyan). |
| − | *** | + | ::*: It should only include the features that are already contributed with minor enhancements: the WAR Products and the OSGi Bundle Facet. Any other planned contributions will not be delivered with Indigo. Most probably, they will be some work done on them during the Indigo time frame, but they will not be a delivery for Indigo. |
| + | ::* IP Logs (M5-M7) | ||
| + | ::*: We need to start providing IP Logs for the project: bug [https://bugs.eclipse.org/338131 338131] (Holger). | ||
| + | ::* Support translations - externalize strings, register in the Babel project (M6) | ||
| + | ::*: Strings are already externalized in the already contributed code: bugs [https://bugs.eclipse.org/337760 337760], [https://bugs.eclipse.org/337762 337762]. | ||
| + | ::*: We need to register the Libra project in Babel: bug [https://bugs.eclipse.org/338109 338109] (Holger). | ||
| + | ::* Ramp Down Planned and Defined (M6) | ||
| + | ::*: We need to define a ramp down policy for Indigo (Kaloyan) | ||
| + | ::* Build with signed JARs (Kaloyan) | ||
| + | ::*: Kaloyan has the necessary privileges for signing JARs. However, there is no automatic integration of signing JARs with the Hudson build yet. Therefore, we need to do this manually. Kaloyan will ask Chris how he does this for the EGit project. | ||
| + | |||
| + | :Bug [https://bugs.eclipse.org/338060 338060] will track the progress of fulfilling the requirements for the Indigo release train. | ||
| + | |||
| + | ;Releases | ||
| + | |||
| + | : For now we plan only official releases that are part of the Indigo release train. We don't plan any other official releases. We will provide Stable Milestone releases and Release Candidates according to the Indigo schedule. | ||
| + | |||
| + | : Our Indigo release will be labeled as "0.1". We think that this is a fair statement. Our first release will include only a tiny set of features from the planned project scope. There is much more to come in the future releases. However, being part of the Indigo release train means that this will be a release of good quality that users and adopters can trust. | ||
| + | |||
| + | : The first Stable Milestone will be labeled as "0.1 M6". | ||
| + | |||
| + | ;Next meeting | ||
| + | |||
| + | :We will make this status call only if necessary. For now let's reserve the current time slot in our calendars. | ||
| + | |||
| + | :Each week we will see if there is any agenda. In case there is, the interested persons can join the call. | ||
Latest revision as of 03:55, 1 March 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. Kaloyan will trigger the process with the Eclipse Planning Council.
- We need to meet some of the requirements of the Simultaneous Release Train by M6. EclipseSource and SAP committers will take the necessary actions to ensure that Libra will meet the requirements on time.
- Planning (M4)
- We need to provide a project plan for Indigo: bug 338129 (Kaloyan).
- It should only include the features that are already contributed with minor enhancements: the WAR Products and the OSGi Bundle Facet. Any other planned contributions will not be delivered with Indigo. Most probably, they will be some work done on them during the Indigo time frame, but they will not be a delivery for Indigo.
- IP Logs (M5-M7)
- We need to start providing IP Logs for the project: bug 338131 (Holger).
- Support translations - externalize strings, register in the Babel project (M6)
- Ramp Down Planned and Defined (M6)
- We need to define a ramp down policy for Indigo (Kaloyan)
- Build with signed JARs (Kaloyan)
- Kaloyan has the necessary privileges for signing JARs. However, there is no automatic integration of signing JARs with the Hudson build yet. Therefore, we need to do this manually. Kaloyan will ask Chris how he does this for the EGit project.
- Planning (M4)
- Bug 338060 will track the progress of fulfilling the requirements for the Indigo release train.
- Releases
- For now we plan only official releases that are part of the Indigo release train. We don't plan any other official releases. We will provide Stable Milestone releases and Release Candidates according to the Indigo schedule.
- Our Indigo release will be labeled as "0.1". We think that this is a fair statement. Our first release will include only a tiny set of features from the planned project scope. There is much more to come in the future releases. However, being part of the Indigo release train means that this will be a release of good quality that users and adopters can trust.
- The first Stable Milestone will be labeled as "0.1 M6".
- Next meeting
- We will make this status call only if necessary. For now let's reserve the current time slot in our calendars.
- Each week we will see if there is any agenda. In case there is, the interested persons can join the call.