[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [eclipse.org-architecture-council] Re: Next Year's Release Train to require being "e4 ready"?
- From: Doug Schaefer <cdtdoug@xxxxxxxxx>
- Date: Tue, 15 Dec 2009 23:56:04 -0500
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=EzLWSdGAKl4m3U2/LgEDL4bcIEwDDEZXyeUL9S2mkC8KhsgIZFe5f1R8zELK2N3iTD 6uQYta9cUPnDdIfFOCIKlt17LB4MyoIATYl1AAicu54YyKcHfzOFSBZTc7boQMhi7NLz ifxWiXvcZY59+f3XlwZNkjOVcwUk9IarZX75M=
The point I was trying to make at the arch council call is that if we wait for e4 to happen naturally, it won't. At the end of the day, it's not even up to the projects, let alone the Eclipse councils whether e4 support is a requirement. It's up to the vendors paying committers to work on the projects. If we want e4 to succeed, as Eclipse councils, we need to do some work ourselves to sell those vendors on the values of e4 and to show how little it's going to cost. And for some that's going to be a tough sell.
What we need to do is have parallel builds of the train against Eclipse 3.x and e4 and show at least a handful of the projects working on e4. We need to put it in the vendors hands and show them the value (hopefully lots) versus the cost (hopefully little). It's got to be real, not just promises.
It's not a simple matter of making this a requirement. At the end of the day, requirements don't really matter, except maybe for the little projects in the outskirts trying to get on the train. Those aren't the ones we care about, the ones that will sell the value of e4.
We've debated many years on what the role of the architecture council should be. This is a gimme. We need to make this happen. Without us, it won't.
On Tue, Dec 15, 2009 at 10:27 PM, David M Williams <david_williams@xxxxxxxxxx>
Its great to see this advance, forward
We have discussed briefly at Planning
Council meetings and so far the reaction of Projects has been "no
plans to anything for e4" but, I'm sure, that's mostly because most
of us simply need education on what it buys us and what we'd have to do
to get it.
But most importantly, I would hope most
of this would be a "bottoms up" requirement and implementation,
where projects found reason to be on e4, and/or implement some advanced
function that could only be done with e4. And if widespread, then we'd
naturally want that commonality codified for the 2011 Simultaneous Release.
Remember, "we are us" when it comes to the Planning Council and
the requirements for Simultaneous Release ... we require very little that
is not already fairly common.
But it is an excellent point we should
all begin to educate ourselves on the implications, and work with our "home
Projects" to understand how to take advantage of e4.
I'd urge care on the message, "e4
ready". One message I've heard is "e4 is completely compatible,
projects need not do anything to run on e4". I don't know the latest,
and don't know if that will always be true, but, we don't want to mistakenly
give the wrong impression to the community that "... it will take
some work to get ready for e4" (unless that is the current message).
And I think a message like "2011 release will be based on e4"
raises the question in Projects of a.) what will that take, and b.) what
do we get for it. I'm not sure those can be answered before EclipseCon,
but would be good to start the discussion, so I will put it on Planning
And, yes, I think a 2 hour joint session
on Sunday is a good idea.
In last week's Architecture Council call,
we discussed the current state of affairs regarding
e4. We concluded that in order for e4 to
gain momentum, it will be extremely important to
make the wider Community aware... and for
Eclipse Projects to start becoming "e4 ready".
All this is still quite some time away, but
we figured that the marketing buzz around releasing
Helios would be a great time to make an announcement
that is very widely heard. If we
could announce at that time that next year's
release train is going to be "e4 ready" if not
"based on e4", that would help
Could you start seeding that idea in the
Planning Council... what the PC members think
about potentially making "e4 readiness"
or "testing against e4" a must-have for next
year's train? What people think about promoting
the EPP Packages to build against /
deliver on top of e4?
What would be a good avenue for "feeding
back" the PC's thoughts into the AC?
BTW, planning for a joint PC and AC (==StAC?)
face-to-face session at EclipseCon 2010
seems like a good idea... who could schedule
eclipse.org-architecture-council mailing list
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.