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 "Epsilon/Agenda"
< Epsilon
Line 1: | Line 1: | ||
Next meeting to be held on the week of '''Apr 16 2012''' | Next meeting to be held on the week of '''Apr 16 2012''' | ||
+ | * Discuss restructuring the Epsilon plugins into more fine-grained features | ||
+ | ** Have a core feature that does not even depend on EMF | ||
+ | ** Be able to install Epsilon in the absence of GMF | ||
+ | ** Currently the Epsilon core feature depends on Eugenia through the ANT task (we can either make all dependencies to non-core tasks optional or split tasks into many plugins) | ||
+ | * Discuss the graduation process | ||
+ | ** Epsilon needs to move out of EMFT as it's an incubator | ||
+ | ** Move to EMF/MMT (ex-M2M)/investigate aiming for a top-level Eclipse project? | ||
+ | * Discuss documenting/automating the (interim) release process. Might be useful if we can share the workload for preparing new releases. | ||
* Decide on what to do with action items carried over (i.e. create enhancement requests in the bugzilla?) | * Decide on what to do with action items carried over (i.e. create enhancement requests in the bugzilla?) | ||
* Go through open bugs | * Go through open bugs | ||
− |
Revision as of 13:00, 17 April 2012
Next meeting to be held on the week of Apr 16 2012
- Discuss restructuring the Epsilon plugins into more fine-grained features
- Have a core feature that does not even depend on EMF
- Be able to install Epsilon in the absence of GMF
- Currently the Epsilon core feature depends on Eugenia through the ANT task (we can either make all dependencies to non-core tasks optional or split tasks into many plugins)
- Discuss the graduation process
- Epsilon needs to move out of EMFT as it's an incubator
- Move to EMF/MMT (ex-M2M)/investigate aiming for a top-level Eclipse project?
- Discuss documenting/automating the (interim) release process. Might be useful if we can share the workload for preparing new releases.
- Decide on what to do with action items carried over (i.e. create enhancement requests in the bugzilla?)
- Go through open bugs