Hi Aurélien,
Athough I am not aware of what are the tasks Michael's team with
work on, here are my 2c.
I don't think that changing of generator (for example moving to
Acceleo) is a priority for GMF-Tooling. The current generator works
well, and we are still able to maintain it without too much
difficulty. Then I think the priority for 3.0 should be set on
functional features and usability. However, if we feel that we
should provide ability to use another generation technology - I
think so -, then the 3.0 could include a first step to provide a way
to plug generators, to propare the future.
Regards,
On 26/09/2011 09:56, Aurélien Pupier wrote:
Hi,
That's good news that GMF-Tooling is reinforced.
A technical question:
You plan to modify the models, will you stay on the same
technology (Xpand/QvTo)?
Otherwise, are you already began the work? If not, when is it
planned?
Regards,
2011/9/13 Anthony Hunter <anthonyh@xxxxxxxxxx>
Hi
Team,
"Anthony,
could
you please approve upgrading the version of GMF-T to 3.0
for the Juno release? "
Well, I suppose the project
lead would
approve first. I am thinking Artem is not around again. We
are still waiting
for his approval for the release review. I am thinking it
may be in the
best interest of the project for Artem to step down as
project lead and
we make Michael Golubev the project lead. To be fair, we
need to give the
community a bit of time to reply back any concerns.
Michael, is it great that
you now have
a team of three of GMF Tooling. I have no opinion either
way if GMF Tooling
is 3.0 in Juno. I would proceed with the project plan and
allow the community
to comment.
Cheers...
Anthony
From:
Michael Golubev
<golubev@xxxxxxxxxxxx>
To:
"GMF Project
developer
discussions." <gmf-dev@xxxxxxxxxxx>,
Date:
09/13/2011 08:06
AM
Subject:
[gmf-dev]
GMF-Tooling
in Juno -- can we plan for 3.0 (major) release
this year
Sent by:
gmf-dev-bounces@xxxxxxxxxxx
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.
I am creating the draft proposal of the
project plan now,
will commit it shortly and post the main proposed topics
here for discussion.
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).
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.
Regards,
Michael
--
Michael "Borlander" Golubev
Eclipse Committer (GMF, UML2Tools)
at Montages Think Tank, Prague, Czech Republic
Montages AG
Stampfenbachstr. 48, CH-8006 Zürich
tel: +41 44 260 75 57
mob: +420 602 483 463
_______________________________________________
gmf-dev mailing list
gmf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gmf-dev
_______________________________________________
gmf-dev mailing list
gmf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gmf-dev
--
Aurelien Pupier
R&D Engineer, BOS Studio
Developer
QA Project Leader
This message and any attachment (the "message")
is intended solely for the addressees and is confidential.
If you receive this message by mistake, please delete it and
notify the sender immediately. Any use not in accordance
with its purpose, any out-spread or disclosure, either as a
whole or partially, is prohibited except with formal
approval. Internet cannot guarantee the integrity of this
message, therefore BonitaSoft will not be liable for the
message if modified.
_______________________________________________
gmf-dev mailing list
gmf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gmf-dev
|
