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 "M2T Meeting 2007-04-12"
(→Agenda) |
(→Agenda: expand sections) |
||
| Line 6: | Line 6: | ||
* Component status | * Component status | ||
| − | * Project | + | :* Code in <code>/cvsroot/modeling/org.eclipse.m2t/</code> CVS? Code to be migrated from <code>/cvsroot/technology/org.eclipse.emft/</code> CVS? |
| + | :* Releng code ready? Releng needs migration? | ||
| + | |||
| + | * Project infrastructure status (see also [[Modeling_Project_Releng_Plan|Modeling Project Releng Plan]]) | ||
| + | :* Bugzilla (components, milestones, descriptions) | ||
| + | :* Public Website (component descriptions, shell for downloads/updates/feeds/news/etc.) | ||
| + | :* Internal Website (for running builds, etc.) | ||
| + | |||
* Should M2T stay an incubating project? The main advantage is the parallel IP process. Some insights on how this can work with some components being leaving incubation while the project remains in incubation: | * Should M2T stay an incubating project? The main advantage is the parallel IP process. Some insights on how this can work with some components being leaving incubation while the project remains in incubation: | ||
| − | + | :* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=175200#c44 Bug 175200, comment 44] | |
| + | |||
* Schedule next meeting | * Schedule next meeting | ||
Revision as of 14:47, 10 April 2007
Time
- Thursday, April 12 @ 1600 UTC
- Local times
Agenda
- Component status
- Code in
/cvsroot/modeling/org.eclipse.m2t/CVS? Code to be migrated from/cvsroot/technology/org.eclipse.emft/CVS? - Releng code ready? Releng needs migration?
- Code in
- Project infrastructure status (see also Modeling Project Releng Plan)
- Bugzilla (components, milestones, descriptions)
- Public Website (component descriptions, shell for downloads/updates/feeds/news/etc.)
- Internal Website (for running builds, etc.)
- Should M2T stay an incubating project? The main advantage is the parallel IP process. Some insights on how this can work with some components being leaving incubation while the project remains in incubation:
- Schedule next meeting