Thanks, Dani, that's more encouraging.
While our service releases have not been true service releases for many years (see the thread that didn't go anywhere on how the yearly release cycle doesn't fit our needs), it isn't critical in my mind for this release to be called Kepler SR3. Would it make folks more comfortable with this if we called this say Kepler J8, published EPP packages in the regular fashion and a simrel repo at a separate http://download.eclipse.org/releases/kepler-j8/ location? This would accomplish the goal of having Eclipse Java 8 support on a stable base in easily consumable form before July and would not surprise any existing Kepler users. Existing Kepler users desiring Java 8 support would need to add the previously-mentioned repository before pulling for updates. Still easier than installing patches and any newly downloaded package would include Java 8 support unless the user downloads from the archives explicitly. - Konstantin From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Megert Sent: Friday, March 21, 2014 1:02 AM To: Cross project issues Subject: Re: [cross-project-issues-dev] Kepler SR3 for Java 8? The announcement was correct, but you need to be aware that it's the first (i.e. 1.0) version of the Eclipse support for Java 8 and as we all know it will have bugs. The Java 8 support comes with big changes in the compiler and other areas of JDT, which means new bugs can also affect users that don't need/want Java 8. This contradicts with the user expectation that each service release will be more stable and have less bugs than the previous drop. Dani From: "Konstantin Komissarchik" <[email protected]> To: "'Cross project issues'" <[email protected]>, "'EPP Developer Mailing List'" <[email protected]> Date: 20.03.2014 18:52 Subject: Re: [cross-project-issues-dev] Kepler SR3 for Java 8? Sent by: [email protected] _____ Hmm. The wording of the Java 8 support announcement left an impression that the support is finished and ready to be used. If it's not, perhaps we should clarify the announcement. On the other hand, if it is ready to be used to the best of everyone's ability, that's all we can ever hope for anyway. Worst case scenario, the user can always roll back to SR2. A single patch repo would be better than hunting for multiple patches, but still leaves a bad impression about Eclipse in the minds of our users. - Konstantin From: [email protected] [ <mailto:[email protected]> mailto:[email protected]] On Behalf Of Markus Keller Sent: Thursday, March 20, 2014 10:31 AM To: Cross project issues; EPP Developer Mailing List Subject: Re: [cross-project-issues-dev] Kepler SR3 for Java 8? I don't think the Kepler repository should get the JDT Java 8 patches. The Java 8 work was a huge effort, and this code has not yet received the in-depth testing that people expect from an official service release. While it adds an eagerly-awaited feature for some users, it also bears quite some risk for all the others that don't need Java 8 support at this time. Luna is coming soon, so the waiting time is not that long. Until then, Java 8 support should not be actively pushed into existing installs. But a common patch for all affected Kepler projects would of course be nice. Markus Keller (Eclipse JDT UI) From: "Konstantin Komissarchik" < <mailto:[email protected]> [email protected]> To: "'Cross project issues'" < <mailto:[email protected]> [email protected]>, "'EPP Developer Mailing List'" < <mailto:[email protected]> [email protected]> Date: 2014-03-20 18:13 Subject: Re: [cross-project-issues-dev] Kepler SR3 for Java 8? Sent by: <mailto:[email protected]> [email protected] _____ >From the perspective of best user experience, we should update the Kepler repository and all the packages. If we limit the changes to just Java 8 support, the test load would not be great. - Konstantin From: <mailto:[email protected]> [email protected] [ <mailto:[email protected]> mailto:[email protected]] On Behalf Of Markus Knauer Sent: Thursday, March 20, 2014 9:46 AM To: Eclipse Cross Project Issues; EPP Developer Mailing List Subject: Re: [cross-project-issues-dev] Kepler SR3 for Java 8? I had this thought, too, and it has been brought up in some discussions at EclipseCon. It should be in our interest to make it as easy as possible for our users to get the integration with Java 8. *If* we decide for a SR3, what would be the deliverables? An update of the packages only? Or only some packages? An update of the common Simultaneous Release repository? Or something else? Thanks, Markus On 20 Mar 2014 09:29, "Mickael Istria" <[email protected]> wrote: It tend to agree with it. Java 8 is something big that we (as tool developers in general) should encourage people to adopt. So it's IMO worth making an exception to the release train and try to get a SR3 that supports it Java 8 out-of-the-box. -- Mickael Istria Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> My blog <http://mickaelistria.wordpress.com/> - My Tweets <http://twitter.com/mickaelistria> _______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev___________ ____________________________________ cross-project-issues-dev mailing list <mailto:[email protected]> [email protected] <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev___________ ____________________________________ cross-project-issues-dev mailing list [email protected] <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
