|Re: [cross-project-issues-dev] Kepler SR3 for Java 8?|
The Planning Council met yesterday and approved creation of Kepler SR2 packages with Java 8 patches installed.
Per the planning council resolution, I sent an e-mail to epp-dev giving the package maintainers an option to opt-out of this. So far, there has been no opt-outs. The deadline to opt-out is by the end of this week. Similarly, I send an e-mail to m2e-dev to confirm that there are no objections to inclusion of m2e 1.4.1 release to clarify previous statements made on this thread. Igor Fedorenko has indicated that they have no objections.
In the meantime, I wrote a script to do the necessary work and the packages are available now.
Of the twelve Kepler SR2 packages, three (cpp, parallel and testing) do not contain any of the patched components and are excluded from this effort.
I am reusing Sapphire’s Hudson instance to build these packages as I am not an EPP committer.
The script downloads all of its own dependencies, including ant-contrib and the various Eclipse bits. All you need to run it is Ant. Copy the script to an empty folder and execute "ant" from this folder.
The part of the script that takes the longest is the download of the Kepler SR2 packages, but the downloads are cached so that if something causes the script to abort in the middle, you will not need to re-download everything.
The Kepler SR2 packages are checksum verified after the download or after fetching from cache.
For each of JDT, PDE, WTP and M2E, the script installs the patch/update if the target is found.
It would be good to start working on the required changes to the downloads page. I opened a bug to track this portion of the effort.
My recommendation is to add “Java 8” as a tab between “Packages” and “Developer Builds”.
On a somewhat unrelated note, I think the existing tab labels could be improved…
Packages – This does not adequately define the content found on that tab since all of the tabs contain packages. How about “Stable” instead?
Developer Builds – This does not define which stream the builds are from. That is, this tab does not lead to developer builds from the maintenance stream nor to i-builds, etc. How about “Luna M6” instead?
If the above proposal is accepted, the tabs would be… Stable, Java 8, Luna M6
Per the planning council resolution, no sign-offs are required from package maintainers. I have done a few basic sanity checks on a couple of packages, but I am mostly relying on automation to ensure the integrity of these packages. If anyone would like to conduct a few tests before these packages are made public, you have until the end of this week to do so.
On Monday, I will need help from an EPP committer or a webmaster to move the packages to their final location. I am not an EPP committer, so I don’t have write access to that area of the downloads server. Does anyone wish to volunteer ahead of time to help me with this? I recommend the following path…
Once the mirrors have been given adequate time to sync, the downloads page changes can be made public and the new packages publicly announced. I hope that we can make this happen by early next week.
Clearly debating this further will not lead to anything productive, so how about this instead…
I will volunteer to write a script that takes existing Kepler SR2 packages, installs the Java 8 patches into them and re-packages them. I will do all the work if I have a commitment to publish these packages at a reasonable location in eclipse.org main downloads area.
I understand your frustration. I think your efforts would be better spent though trying to convince the community to action with hard data, like the number of users who are switching to Java 8 right now that can't figure out how to install the feature patch. Is there a bug report where this is being gathered?
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [cross-project-issues-dev-bounces@xxxxxxxxxxx] on behalf of Konstantin Komissarchik [konstantin.komissarchik@xxxxxxxxxx]
You seem to be saying that I don’t know how these releases are put together or who does the work. That’s low.
You are quite right that there is no consensus. It is quite sad to see this. There is lots of talk about needing to make ensure that Eclipse remains competitive, but when time comes to do something concretely towards that, there is little interest. Let there be no mistake, it is a bad completive position to have Eclipse ship official Java 8 support three months behind the competition. For developers immersed in Eclipse internals daily, it may not seem like a big deal to ask users to seek out and install various patches or to use a Luna pre-release build or to just wait, but average users don’t see it that way.
Yes, you have to remember, the Foundation doesn't put together releases, the projects do. And Mike is correct, there isn't consensus from the projects that a Kepler SR3 is warranted versus putting resources on Luna. The feature patch install is easy and just needs to be made more visible, as Mike is proposing to do.
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [cross-project-issues-dev-bounces@xxxxxxxxxxx] on behalf of Mike Milinkovich [mike.milinkovich@xxxxxxxxxxx]
On 27/03/2014 1:28 PM, Konstantin Komissarchik wrote:
Back to the top