I actually added more information in the bug mentioned by Ernesto, below.
Basically, we need to align the product management vision and the product/project engineering artifacts. One of the problems, as eloquently stated by Peter in the bug, is that we have many usages/definitions for “product” and we need to harmonize this so we can more effectively communicate. We are, after all, breaking new grounds at Eclipse by doing product management…
This is what I wrote in the bug, for the Zeligsoft folks are still locked out:
In the meantime, please see inline below.
I think the discussion in Bug 502133 covers it.
So there are different meanings of "product", and Céline, correct me if I'm wrong, but I think you are asking about the "product" in the sense of what we package and deploy, as specified in the papyrusrt.product file, is that right?
My understanding from the discussions with Charles and Simon and in the bug, is that codegen and rts should be there for 0.8 (although not xtext), even if they are not considered the "base" set of features in some sense. I think this makes sense, because otherwise there would be a mismatch between what is installed by the Oomph setup and this packaged product. Furthermore, if a user downloads this product she would have to explicitly add the codegen update site to get the same set of features.
PS: I'm responding here rather than in the bug because we are having connectivity issues with the Eclipse servers from our office.
-- Ernesto Posse Zeligsoft Hi,
I think that the current included features in the the basic Papyrus-RT feature is what should be there. So that looks good to me.
What is missing in that picture is the optional migration, compare and Xtext features.
What I would like too see is the code-gen and run-time features to be included in some top level C++ feature. If that is the current C++ core feature, or a new C++ feature, which then includes the current C++ core feature and the code-gen and run-time features I cannot say. But this should be anyway be separated from the basic Papyrus-RT feature (as indicated in the picture).
/Peter Cigéhn
<cr> This is a good list of basic features. The only other basic feature I could see in here would be “Oeprt.umlrt.tooling.compare.feature” because I see this as a rather important aspect of any development and especially for the proper support of a DSML.
What do you mean by “not included by default”? From the definition of the product (Eclipse project page), some of these will need to be included in the final (product management) product. Some of these are also part of the previous milestone and not providing them could be considered a regression, unless we ensure that proper installation warnings and documentation is provided (e.g., a warning that some parts are now optional or explicitly showing what is to be installed or not where user discovery of these options is not optional). According to the Eclipse guidelines, this is something that can be done in a minor version change, but we need to ensure that it is very visible and transparent. Given the v0.8 timeframe, I would prefer that this installation change be done in v0.9 or 1.0, where we would have more lead time to “educate” our users.
I would probably group some of these together. for example, everything related to generating an executable for a particular language. However, I am not sure if that matches the meaning of the features from a development team point of view...
What do you mean by "work on his [sic!] own”? If you mean the minimum configuration that would let you create a UML-RT model, that is probably correct. From the project definition and what was provided in v0.7.2, I would expect to be able to create a UML-RT model, to generate its code, and to compile and run it, which would not be the case with only the basic features as described above. On the other hand, I can see the future need for the basic set as described above (e.g., to have a “Papyrus-RT for DSML toolsmiths” variant).
Understood. However, we still need to make the link between the (product management) product and this (engineering) product.
</cr>
<image001.jpg>_______________________________________________ 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
|