[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [eclipse.org-architecture-council] RE: Next Year's Release Train to require being "e4 ready"?
|
+1
Wayne
Donald Smith wrote:
Are people generally open to the idea of meeting Sunday afternoon again?
- Don
*From:* Oberhuber, Martin [mailto:Martin.Oberhuber@xxxxxxxxxxxxx]
*Sent:* December 15, 2009 1:47 PM
*To:* david_williams@xxxxxxxxxx; donald.smith@xxxxxxxxxxx
*Cc:* eclipse.org-architecture-council
*Subject:* Next Year's Release Train to require being "e4 ready"?
Hi David,
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".
http://wiki.eclipse.org/Architecture_Council/Meetings/December_10_2009
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 a lot.
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 this?
Thanks,
Martin
------------------------------------------------------------------------
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
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.