Re: [gmf-dev] GMF-Tooling in Juno -- can we plan for 3.0 (major) release

[Mickael Istria <mickael.istria@xxxxxxxxxxxxxx>]

On 13/09/2011 14:05, Michael Golubev wrote:

Hello, 

While we are waiting for a release review for GMF-T 2.4, I would invite everyone to put efforts into the planning for next release.

I am glad to confirm that for this year we have got a sponsorship from Avaloq Evolution AG, which is willing to support team of 3 developers working specifically on GMF-Tooling.

That's very good news. Congrats for attracting so much interest and sponsorship in GMF-Tooling. I can imagine this was not an easy work!

I am creating the draft proposal of the project plan now, will commit it shortly and post the main proposed topics here for discussion.

Great. I think some of the topics we should think about improving, according to what we can read on the forum are:
* Integration with CDO/Dawn
* integration with EEF to provide also customization of properties. Not make a strong dependency of GMF-Tooling onto EEF, but making it easier for people to think about using EEF when developing diagrams.

Also, technical stuff:
* Make GMF-Tooling models and templates extensible in order to be able to provide new features in models from extension mechanism. (Such as SVG will come with extension for the model + extension for the templates + extensions for the runtime).

However, it is already clear for me that in order to deliver the new features we need Juno release to be a major one, thus 3.0 instead of 2.x. 

The reason is, we will have to change models significantly, and we will not be able to provide automatic backward compatibility with the models created for 2.4.x 

(we will of course follow the transition procedure from the past of GMF-T and will develop 'Migrate Model' actions to support migration of existing models).

I +1 this proposal. Until then, GMF-Tooling release and versioning was trying to follow the same rythm than GMF-Runtime, but the last monthes clearly show that the project cannot really work like this any longer. Then it would make a lot of sense to start a new 3.x stream with lots of new features.

Anthony, could you please approve upgrading the version of GMF-T to 3.0 for the Juno release? 

Also I am not sure how we can add into the Bugzilla the new set of milestones (no matter whether it is 3.0 M2, M3... or 2.5 M2, M3...). 

If someone know how to do that please advice me, it would help with pushing the project plan proposal into Bugzilla.

I remember Anthony told that could be done only by project lead. I think also a good time for you to replace Artem in this role ;)

--

Mickael Istria
R&D Engineer, Eclipse Plug-in RCP Developer

PetalsLink - Open Source SOA

My blog - My Tweets