If people are interested, I am hosting an e4 Evangelist call today at
1pmET. The topic of conversation is how do we structure an e4 landing
page and communicate the appropriate message for e4.
The call-in numbers are:
Participant
Passcode:
874 515 514#
Canada:
1-877-727-8553
Canada
Caller Paid: 416-840-9801
U.S.
1-866-394-4146
U.S. Caller
Paid: 1-480-629-1624
Germany:
0800-111-1193
Germany Caller paid
49-6958-999-0561
UK:
0800-358-3473
UK
Caller Paid: 44-207-154-0023
France:
0800-94-0253
France
Caller Paid: 33-1-70-99-3261
Sweden:
0200-125-713
Sweden
Caller Paid: 46-850-520-161
Finland:
0800-114-845
Finland
Caller Paid: 358-969-379-456
On 4/28/2010 10:17 AM, Eric Clayberg wrote:
I agree 100%. We are already seeing our commercial
customers starting to ask (e.g., demand to know) when we will be
supporting Eclipse 4.0 with all of our products. The perception is
definitely out there that 4.0 is the next great release of Eclipse and
that 3.6 is just an (minor? maintenance?) update to the "old" 3.x
version. Anyone who reads these lists or pays close attention to what
is really going on in Eclipse-land knows better, but that is a small
minority compared to the huge mass of Eclipse users out there who will
simply assume that 4.0 is the latest and greatest and the place they
should be as soon as it is released. Those folks will likely be very
disappointed if they try to immediately move to 4.0 and discover that
only a handful of Eclipse.org projects and 3rd party plugins actually
support it. Some sort of (strong) qualifier (Preview, Beta, Early
Availability, Early Adopter, etc. are all good) is definitely needed to
mitigate the possible damage to the Eclipse brand and ecosystem and set
the proper expectations in the minds of the early adopters (and keep
the number of those early adopters to a manageable level).
-Eric
This is a great example of the problem we're
facing, and this is just an
early example. People are eagerly awaiting Eclipse 4.0, the next
generation eclipse. You can message until you are blue in the face, but
that isn't going to stop the perception that if you call it 4.0, it's
that 4.0.
So yes, please call this a Preview release or something along that
line.
-----Original Message-----
From: eclipse-dev-bounces@xxxxxxxxxxx
[mailto:eclipse-dev-bounces@xxxxxxxxxxx] On Behalf Of Jeff McAffer
Sent: Wednesday, April 28, 2010 9:36 AM
To: General development mailing list of the Eclipse project.
Subject: Re: [eclipse-dev] Re: [e4-dev] Eclipse Project 4.0 Release
There could of course be many nuances missed by Google translate but
the
article seemed mostly like a distillation of John's recent e4/Eclipse
4.0 clarification post. I don't think they particularly cast the
situation differently (at least not by that translation).
The problems with expectation that arise are inherent in the naming
(Eclipse 4.0). As discussed that naming implicitly leads one to believe
that this is "the Eclipse 4.0 SDK" and it is the "logical successor to
3.6". If we are not comfortable with everyone downloading and using
it, then the naming should reflect that with some sort of qualifier
(e.g., "Preview", "Beta", "Early Availability", ...). IMHO this sends
a
clear, representative and appropriate message to the community.
Boris' interview article pointed out that we are targetting the 2011
release train. This is nice positioning. It may be a little to subtle
however. That is, its not clear that people will say "hmm, its not on
the simultaneous release so it is not stable/bug-free/..." (frankly, we
don;t want to promote that idea either). Perhaps we can combine the
approaches and talk about the upcoming Eclipse 4.0 SDK as the
"Indigo/Isaac preview"?
Jeff
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev
|
