Skip to main content

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.

Jump to: navigation, search

Papyrus IC/Architecture/MoM/2018-05-15 Architecture Committee Minutes

Attendees

  • Rémi (chair)
  • Ernesto (Zeligsoft)
  • Keith (OneFact)
  • Ansgar (CEA)
  • Per (Combitech)

Next Phone call: July 3rd, 2018, 4PM

Topics

Welcome: Ansgar (CEA)

UML2 And Photon

No other contributions?

Collaborative meetings

  • Discontinued?
    • volunteers: Ernesto & Philip
  • PM committee decide for lower priorities

Task Forces

Ansgar: Next year plan

  • Roadmap for Photon (see Photon)
  • Next version: 4.0.
    • API: need some major improvements
    • Copy and Paste issues (Antonio) - news?
  • Currently up-to-date

Philip: DSML task force

  •  ?

Philip/Ernesto: Textual / graphical modeling

  • No news

Per/Rémi: Dependency management, dependencies from Papyrus

  • no update on that task

Release train for Papyrus

Oxygen Plan

  • Oxygen.3: released (End of March 2018)
  • Oxygen.4 (not in simultaneous release train, only on official Papyrus updates): planned for end of May 2018 Oxygen.4 plan

Photon Plan - +3 binary build date

  • M7: May 16th, 2018
  • RC1: May 23rd, 2018
  • RC2: May 30th, 2018
  • RC3: June 6th, 2018
  • RC4: June 13th, 2018 - to be release as Photon if OK

Additional topics

  • Release engineering
    • Volunteers?
    • No proposals yet. CEA is running the releng on its own
  • Release train for Photon +1 (Rémi)
    • feedback from CEA?
  • Photon & Oxygen: Minor release and API breakage (Ernesto)
    • Brought up by Charles in February
    • This topic came because it could break the Papyrus-RT builds
    • Quentin & Ernesto discussed on the technical aspect
      • Issue from Junit tests => issue mostly resolved (from Photon, JUnit plugins will be released - initial problem fixed)
      • 20 plugins with major API changes
    • Proposal:
      • Papyrus community version?
      • Specific branches for specific subprojects/users
        • To be raised to product management and/or steering committee?

Back to the top