Community
Participate
Working Groups
Within the Kepler timeframe the main goal of the migration back to the Xtend2 template language was to have two separate set of templates producing identical outputs. Also this goal is not yet delivered in Kepler R, and deferred to Kepler SR2, it is clear that maintaining 2 set of templates languages at the same time forever is impossible. GMF-T is still going to have a specific build around Kepler SR2 time (TBD whether we need a separate release here) which will have Xtend2 and old Xpand templates producing character-by-character identical generation results. This release will be published as an escape for users who don't want to migrate their extensions to the new templates. After that GMF Tooling will declare the old set of XPand based templates deprecated, and the further development will go to the Xtend2 templates only. We will need to decide how to do that in such a way to reduce the hurt dealt to those GMFT users who had significant investments into the extensions targeting the old set of templates. Within Luna timeframe it is expected that some of the features still will be developed in parallel for Xpand and Xtend2 templates, but the deprecation of the old proprietary language in favor to the modern and de facto standard one should be clear.
