[mdt-papyrus.dev] Maintaining the Oomph Setup(s)

[Christian Damus <give.a.damus@xxxxxxxxx>]

Hi, Team,

Thanks for the recent updates about the removal of “extra” components to separate repositories during the Neon release.

The Papyrus Setup model provides, still, some of these components for import on the Neon stream from the main Papyrus git repo, which now wouldn’t make sense.  Could the component owners please ensure that the Neon stream of the setup model is updated to correctly reflect these changes?  I see these possibilities for update:

• reconfigure a component’s Neon stream to clone the new Git repository and import projects from that
• delete a component’s Neon stream, with sub-options to:
• provide a new Oomph Setup model published in the official index
• don’t provide any Oomph Setup solution for Neon

In all cases, the Mars streams in the Papyrus Setup can be left as is, because these projects are all still integrated in the Mars maintenance program.

These projects still have Neon streams in the Papyrus setup, but are now in separate Git repositories:

• Papyrus Designer (Java, C++, Qompass)
• RobotML
• Papyrus-RT

Of these, Papyrus-RT is actually a separate Eclipse Project, so I think it doesn’t belong in the Papyrus Setup model at all (for Neon).  Are any of these other components likewise planning to reconstitute as new Eclipse Projects?

These projects already have removed their Neon streams from the Papyrus Setup (thanks):

• Moka
• SysML 1.4

Cheers,

Christian