Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "ECF Conference Call 9.23.2008"
(New page: ==Attendees== ==Agenda== *Move to runtime *Automated testing *2.0.1 service release *2.1 Minor Release *Planning for ECF 3.0) |
|||
| Line 3: | Line 3: | ||
==Agenda== | ==Agenda== | ||
| − | + | ===Move to runtime=== | |
| − | *Automated testing | + | *Stay with CVS for now...as use of ECF in p2/platform makes subversion usage more cumbersome. It may be possible to use Subversion for components of ECF in future. |
| − | *2.0.1 service release | + | *See [[ECF Migration to Runtime Project]] to verify new module structure and that all necessary existing modules are to be copied over. Make changes to page if things missing or wrong. |
| − | *2.1 Minor Release | + | ===Automated testing=== |
| − | *Planning for ECF 3.0 | + | *Ted and Markus are talking about changes to build to do automated testing. |
| + | ===2.0.1 service release=== | ||
| + | **Contribution to Ganymede 3.4.1 service release complete. After Ganymede service release Scott will do a build for ECF download page. | ||
| + | ===2.1 Minor Release=== | ||
| + | *See [[ECF/Plan for 2.1]]. Also Scott would like to introduce org.eclipse.ecf.storage plugin. *See /cvsroot/technology/org.eclipse.ecf/plugins/org.eclipse.ecf.storage and ../tests/org.eclipse.ecf.tests.storage. | ||
| + | *Markus and Jan will check with Sharon and then commit jSLP RC5 to ECF repository. After that is complete then build will be updated. Hopefully can happen in time for 2.1. | ||
| + | ===Planning for ECF 3.0=== | ||
| + | *See [[ECF/Plan for 3.0]]. | ||
| + | *Need to restructure ECF features for easier (p2-based) consumption. See '''Reorganize/restructure ECF Features''' on [[ECF/Plan for 3.0]]. | ||
| + | *'''COMMITTER ACTION''': All committers review [[ECF/Plan for 3.0]] and report to mailing list whether their area and availability matches plan with what is there. Scott needs input on the plan so that he can construct an xml-based plan that is reasonable/rational given people's availability for ECF. | ||
Revision as of 10:53, 23 September 2008
Contents
Attendees
Agenda
Move to runtime
- Stay with CVS for now...as use of ECF in p2/platform makes subversion usage more cumbersome. It may be possible to use Subversion for components of ECF in future.
- See ECF Migration to Runtime Project to verify new module structure and that all necessary existing modules are to be copied over. Make changes to page if things missing or wrong.
Automated testing
- Ted and Markus are talking about changes to build to do automated testing.
2.0.1 service release
- Contribution to Ganymede 3.4.1 service release complete. After Ganymede service release Scott will do a build for ECF download page.
2.1 Minor Release
- See ECF/Plan for 2.1. Also Scott would like to introduce org.eclipse.ecf.storage plugin. *See /cvsroot/technology/org.eclipse.ecf/plugins/org.eclipse.ecf.storage and ../tests/org.eclipse.ecf.tests.storage.
- Markus and Jan will check with Sharon and then commit jSLP RC5 to ECF repository. After that is complete then build will be updated. Hopefully can happen in time for 2.1.
Planning for ECF 3.0
- See ECF/Plan for 3.0.
- Need to restructure ECF features for easier (p2-based) consumption. See Reorganize/restructure ECF Features on ECF/Plan for 3.0.
- COMMITTER ACTION: All committers review ECF/Plan for 3.0 and report to mailing list whether their area and availability matches plan with what is there. Scott needs input on the plan so that he can construct an xml-based plan that is reasonable/rational given people's availability for ECF.