[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [gmf-dev] GMF Tooling missed M7
|
Hi Mickael:
A quick reply to your comments.
1) Build:
The build technology at Eclipse has
been a long standing nightmare and as you have discovered is by far the
most frustrating aspect of Eclipse projects.
Four or more years ago we had N different
build systems for the Eclipse modeling projects. Then around three years
ago, through the efforts of IBM, we were able to consolidate all the modeling
builds onto the Common Modeling Build. The Common Modeling Build was managed
by a full time IBM release engineer (Nick Boldt). When Nick left IBM, my
team was not able to replace him, so the Common Modeling Build became stale.
In the last two years, we have moved back to the dark ages of N different
build systems: Nick started Athena, a bunch of teams are using Buckminster,
others are using Tycho and whatever else exists for builds out there.
The builds I manage have two web pages
provided by the Common Modeling Build, a start a build page and a promote
a build page. I am not moving any of the builds I manage until the N different
build systems provide similar capabilities. No doubt a bunch of developers
are going to reply to this email telling me how great their build is. Hopefully
we can all document our builds on the wiki so we can verify the technology
and then we can have a conversation about all the modeling projects moving
to the same build technology again so we can help each other. I am the
only committer on the Common Modeling Build, so I am maintaining it to
make sure it works. This is not enjoyable.
2) No real plan for contributing to Indigo:
There is clear documentation for contributing to Indigo.
http://wiki.eclipse.org/index.php/Indigo_Simultaneous_Release
have links to the process.
The 1+, 2+ 3+ for the Eclipse Simultaneous
release does not work for modeling and never has worked. I blogged about
it here http://ahuntereclipse.blogspot.com/2010/05/helios-rc1-1-2-3-go.html
. You have to work with your dependencies and start you builds after they
have done their M7 builds. In fact that the GMF Runtime was completed "early"
for M7, I had it done the morning of the 2nd so this is a early 2+.
3) Not enough contributors
This is a reality for most of the Eclipse
projects in Modeling.
Now that you have stepped forward and
committed to actually getting things done on GMF Tooling, we should consider
the removal of the current project lead and have you take over.
Cheers...
Anthony
From:
Mickael Istria <mickael.istria@xxxxxxxxxxxxxx>
To:
"GMF Project developer
discussions." <gmf-dev@xxxxxxxxxxx>,
Date:
05/05/2011 04:09 AM
Subject:
[gmf-dev] GMF
Tooling missed M7
Sent by:
gmf-dev-bounces@xxxxxxxxxxx
Hi all,
Yesterday was the deadline for M7, and unfortunately, GMF Tooling could
not be part of it. I sadly think it is time to forget the idea to deliver
GMF Tooling as part of Indigo... Although I think we can still deliver
a release at the same time as Indigo.
In my opinion, this is bad news, but that simply means that we need more
preparation for next release train. Here are some things that could help
next year:
Issue for Indigo: Difficulty to get the status and contents of a build
Solution for Juno: Have builder on hudson.eclipse.org
Issue for Indigo; Difficulty to run a build locally, and then to contribute
Solution for Juno: Improve builder
Thoughts: I think the Athena / Modeling common builder is quite difficult
to use, fix, tweak and understand. It is also difficult to get help on
this. Tycho is a good alternative.
Issue for Indigo: No real plan for contributing to Indigo
Solution for Juno: Have a plan, with fixed dates
Thoughts: Since GMF-Tooling depends on GMF-Runtime, we need to have a calendar
in order to ensure GMF-Runtime is build early enough for GMF-Tooling to
be built on time.
Issue for Indigo: Not enough contributors
Solution for Juno: Boost GMF Tooling contributors number by making it easier
to get in the project. and blogging, and trying to get the "Most Open
Project" award. I think there a lot of GMF users, let's turn them
into contributors!
Thoughts: Blogs, talks, JUGs...
I also have some difficulties to get how the GMF repository is organized,
Who is in charge of building it, where does it gets the artifacts of each
component...? Having a look to http://wiki.eclipse.org/Modeling_Project_Releng/Releasing
confused me more than it helped me.
I think after Indigo, it would be sane for GMF to re-think the way it is
built, aggregated and so on. I also noticed some inconsistencies in features
naming that make it even more complicated to understand which component
provide which feature.
I am very frustrated that GMF-Tooling missed this release train, I won't
let it happen next time ;)
Regards,
--
Mickael Istria
R&D Engineer
Best
Eclipse Modeling Tool 2011
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
