Nice work, Camille. It looks like all of the bits are in place to restore the migration feature.
However, we still need to come to a decision on how to proceed. If we intend to graduate with a 1.0 release, then AFAIU it’s an all-or-nothing deal. No part of that release may be in incubation. So, if the migration component is to release as a 0.10 then it will have to be a separate build with a separate deployment and installation from a separate p2 repository. (note that version numbering doesn’t have to correlate to incubation status, but it is helpful to users)
Otherwise, if we want to graduate the migration feature too, then of course its dependencies in Papyrus must be released as non-incubation, too.
The EMO’s
Wiki page about incubation talks exclusively in terms of Project. The migration component is not a Project; Papyrus-RT is. Has anyone discussed the details of our plan with Wayne/EMO? Maybe it only matters to conform to the Incubation guidelines if we wanted to use the parallel IP process, which we don’t?
On Jun 21, 2017, 07:36 -0400, Camille Letavernier <cletavernier@xxxxxxxxxxxxxxxxx>, wrote:
Thanks, Christian!
It took me some time to figure out how the build was configured (I initially thought the migration was part of the tooling, but that's not exactly true :) ), so your rebase probably cleans up a few things :)
This commit was part of a commits chain, so I've rebased the other 3 commits on top of it. The Gerrit-Migration build should be green after that
Camille
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev