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 "GMF Dev Calls"
(→Items for the next call) |
(→Items for the next call) |
||
| Line 16: | Line 16: | ||
What is our strategy regarding backward/forward compatibility story? | What is our strategy regarding backward/forward compatibility story? | ||
| + | |||
| + | GMF Diagram Runtime needs to start thinking about the canonical edit polices issues raised by the Code Gen Team, specially the ones that require conceptual change in the way canonical edit policy works, also we need to agree on the severity | ||
=== Previous call notes === | === Previous call notes === | ||
Revision as of 16:23, 21 May 2007
This page contains topics for upcoming GMF Developer conference calls, along with links to previous call notes. Calls are tentatively scheduled for every other Tuesday at 11:00 am Eastern US time, using the dial-in information below:
Toll Free Dial In Number: (888) 476-6128 Int'l Access/Caller Paid Dial In Number: (517) 267-1462 PARTICIPANT CODE: 888691
If no topics appear, or it seems we can wait until the following call to cover those listed, we will cancel the call the Monday prior.
Items for the next call
Date: May 22, 2007 at 11:00 am Eastern
We need the patch attached to bugzilla 180772 NLS33: Unexternalized string in problems filter to be submitted by the code gen team
Is there any plan on the Code Gen side to start Profiling the Performance, Memory Consumption and Memory leaks in the generated code?
What is our strategy regarding backward/forward compatibility story?
GMF Diagram Runtime needs to start thinking about the canonical edit polices issues raised by the Code Gen Team, specially the ones that require conceptual change in the way canonical edit policy works, also we need to agree on the severity