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 "VIATRA/DeveloperMeetingMinutes/Meeting20130521"
Line 1: | Line 1: | ||
− | |||
== Topics == | == Topics == | ||
− | === Bugzilla | + | === Bugzilla cleanup policy ==== |
− | + | * created version "0.8.x" | |
− | * | + | * assigned version field correctly |
− | * | + | |
** M3-M4 within 0.7.x for now, Mx can be reused for 0.8.x later on | ** M3-M4 within 0.7.x for now, Mx can be reused for 0.8.x later on | ||
** ---/0.8.x contains issues that are planned to be addressed | ** ---/0.8.x contains issues that are planned to be addressed | ||
** Future/unspec contains "future" issues | ** Future/unspec contains "future" issues | ||
− | + | === Issues to be discussed === | |
* M3 | * M3 | ||
** can https://bugs.eclipse.org/bugs/show_bug.cgi?id=405291 be closed? | ** can https://bugs.eclipse.org/bugs/show_bug.cgi?id=405291 be closed? | ||
Line 23: | Line 21: | ||
*** https://bugs.eclipse.org/bugs/show_bug.cgi?id=399139 (@Constraint strings escaping) | *** https://bugs.eclipse.org/bugs/show_bug.cgi?id=399139 (@Constraint strings escaping) | ||
− | == Discussions with Ed | + | == Discussions with Ed == |
+ | * "Xtext 2.3 vs 2.4": Ed recommends to go with 2.4 for the 0.7 release already, create backwards compatible version only on demand | ||
+ | * Preparations for the release: ''You need to produce a short set of slides/pages that include a summary of the IP contributions in that release. If you follow the cross projects mailing list you'll see Ed Willink posted some notes about links for querying such a summary. Best to have a look at what some other projects have done for past releases.'' | ||
+ | * Moving out of incubation: ''It's too late to join Kepler for this release. As part of a release review, you can do a graduation review as well. It's basically the same thing.'' | ||
+ | * Xcore integration: He'll take a look at our proposal (very little time before Kepler). We should opt for an extension (rather than direct modification) of Xcore, if possible. |
Revision as of 06:16, 20 May 2013
Topics
Bugzilla cleanup policy =
- created version "0.8.x"
- assigned version field correctly
- M3-M4 within 0.7.x for now, Mx can be reused for 0.8.x later on
- ---/0.8.x contains issues that are planned to be addressed
- Future/unspec contains "future" issues
Issues to be discussed
- M3
- can https://bugs.eclipse.org/bugs/show_bug.cgi?id=405291 be closed?
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=404952 (erroneous project registration) is worrying
- M4
- interesting (needs assignee)
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=398758 (Map view of matches?)
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=404262 (NPEs are flying when moving EIQ files around)
- dubious
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=398735 (IQException dependency chain)
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=398911 (Type checking of EJavaObject)
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=398775 (pattern def traceability of engine)
- "can it be closed?"
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=399139 (@Constraint strings escaping)
- interesting (needs assignee)
Discussions with Ed
- "Xtext 2.3 vs 2.4": Ed recommends to go with 2.4 for the 0.7 release already, create backwards compatible version only on demand
- Preparations for the release: You need to produce a short set of slides/pages that include a summary of the IP contributions in that release. If you follow the cross projects mailing list you'll see Ed Willink posted some notes about links for querying such a summary. Best to have a look at what some other projects have done for past releases.
- Moving out of incubation: It's too late to join Kepler for this release. As part of a release review, you can do a graduation review as well. It's basically the same thing.
- Xcore integration: He'll take a look at our proposal (very little time before Kepler). We should opt for an extension (rather than direct modification) of Xcore, if possible.