[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] Performance, 3.8 versus 4.2
|
Was Juno a good point in time to introducing such a change? I say YES. Why? Because as the current situation shows us, ppl don't try things until they are forced to do so and that should we have chosen to wait until Kepler then the same discussion would have happen but in September 2013. And don't try the argument that you would have tried it. After all eclipse 4.1 was released in July 2011.
I completely agree with Pascal on this point. If we didn't ship this year we would have simply delayed the problem. Of course, many people would have liked the small group of platform committers to have delayed the release until they managed to fix everything (in an open and transparent way, all for free), but that wasn't going to happen. To get the kinks worked out of a major release, we need your help!
Also remember, the Eclipse platform team shipped both Eclipse 3.8 and 4.2 so we could transition more easily. However, there will not be an Eclipse 3.9, so if the 4.x platform is not useable for your needs, now would be the time to step up with some resources.
Of course, many of the people who will follow this discussion are the ones up late at night, working on Eclipse on their own time. I'm not sure that asking this group to do more is the answer. But, if you're going to complain, please ask yourself: "Did I do enough for this release, or am I getting out of the Eclipse platform exactly what I put in?".
But more importantly than all this is the meta conclusion that the era of being able to take the platform for granted is over and that we are all going to have to pay more attention to it, roll up our sleeves and contribute.
Maybe this is the wake-up call we all needed, or maybe it's simply another "yeah, things need to improve and someone else better do it". :-|
Cheers,
Ian
Pascal
--
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com |
http://twitter.com/eclipsesource
