Skip to main content

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.

Jump to: navigation, search

VIATRA/DeveloperMeetingMinutes/Meeting20171102

< VIATRA‎ | DeveloperMeetingMinutes
Revision as of 08:53, 14 November 2017 by Zoltan.ujhelyi.incquerylabs.com (Talk | contribs) (Created page with "== Topics == * {{VIATRA-Status}} * TODOs from last meeting ** TODO Ábel: Add more details to CPS benchmark readme * Updated VIATRA website ** http://eclipse.org/viatra ** No...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Topics

Minutes

  • CPS benchmark readme updated
  • VIATRA website
    • Any feedback welcome
      • Main title: Scalable reactive model queries and transformations
      • List of partners could be extended
  • Documentation
    • Target website _and_ help
    • Use similar formatting to tutorial
    • Goal: deprecate wiki.eclipse.org (with explicit links to modified contents)
  • 1.7 release
    • M3 out, feature freeze
    • Issues requiring development mostly fixed
    • Some testing/documentation issues still open
    • TODO: Gaben: review optimization tickets, split/close/postpone as necessary
  • 1.6.2
    • Regression: excessive logging because a mistake
    • Fix already in 1.7, backport waiting for review
  • Feature request
  • VIATRA 2.0
    • Review and discussion of components to be migrated to 2.0, conclusions
      • CPP components
        • Development effort in a hard fork of the project
        • Cannot be merged back soon
        • For now remove; if necessary, can be readded later
      • Keep Graphiti and Facet model editors (remain in incubation)
      • Keep LS debugger as incubation component
      • TODO Zoli (Ábel): Check usage of EVM-JDT integration in Papyrus
    • DSE maintainer needed
    • High-level feature ideas discussed four weeks ago
    • Low-level issues in Bugzilla with 2.0 milestones
      • Issue list is up to discussion
      • Some bugs still not opened
      • Currently issue list seems ambitious
    • 1.7-maintenance branch is planned to be created between 13-17 November

Back to the top