First, import of RSA models is not part of the MVP for v1.0. Given the discussion below, I would think that is should not be part go the 1.0 release.
Second, it appears that this may be more than would be acceptable in a 1.0.1 release, so it should be considered for the 1.1 release.
Third, the model import will not be a “project” in the Eclipse sense. It will be a component in an upcoming Papyrus-RT release.
That being said, the discussion below is warranted, but it cannot supersede the current product plan. We need, must, concentrate on aspects that have been identified for the release.
Regards,
Charles Rivet Senior Product Manager, Papyrus-RT product leader
Yes, Eclipse doesn’t require a correlation between version numbers and incubation status, especially for projects that had already produced releases before moving to Eclipse and incubating there.
I am inclined to agree with Peter that import is not ready for graduation and if it is to be an incubation component, then that should be called out in the Graduation Review materials to give the community, Modeling Project, and EMO an opportunity for comment. So, yeah, let’s keep those patches on ice.
Cheers,
Christian
On Jun 22, 2017, 03:49 -0400, Camille Letavernier < cletavernier@xxxxxxxxxxxxxxxxx>, wrote:
Hi,
I don't have any specific opinion on the version numbers and incubation status. We've been living with Incubating/Non incubating components in Papyrus for some time, so we can probably do the same in Papyrus-RT. If it's just a matter of keeping v0.9.0 instead of 1.0.0, and (Incubation) in the feature/plugins name, then that's fine. I think the migration feature is already a distinct one (Same update site, but not directly part of the tooling), so this doesn't seem to imply any additional work (e.g. restructuring)
Regarding this question:
> In any case, probably this means that we can proceed with your gerrit patches. Are we all agreed on that?
We still rely on a temporary update site hosted on Papyrus Hudson, so I don't think it's a good idea to merge the patches yet. I don't know when the actual release of Papyrus-RT is planed, but I'd prefer to be sure that the required Papyrus bits are available first, rather than push now and revert later :)
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
_______________________________________________ papyrus-rt-dev mailing list papyrus-rt-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|