Re: [cross-project-issues-dev] Kepler SR3 for Java 8?

[Miles Parker <miles.parker@xxxxxxxxxxx>]

+1 on not putting Java 8 patches in Kepler.

I don’t have any reason to insert myself here except as a consumer, but my strong feeling is that we should take the advice of the team actually building the tool. Service Releases are just that. They are aimed at providing updates to existing features. Users rightly expect to have an increasingly stable and predictable platform from one SR to the next, not a change w/ very large scope and implications across many components. Even if it is everything that anyone has a right to expect as to release quality (as I’m sure it will be :))), it’s bound to be destabilizing.

On Mar 20, 2014, at 10:31 AM, Markus Keller <markus_keller@xxxxxxxxxx> wrote:

> 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" <konstantin.komissarchik@xxxxxxxxxx> 
> To:        "'Cross project issues'" <cross-project-issues-dev@xxxxxxxxxxx>, "'EPP Developer Mailing List'" <epp-dev@xxxxxxxxxxx> 
> Date:        2014-03-20 18:13 
> Subject:        Re: [cross-project-issues-dev] Kepler SR3 for Java 8? 
> Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx 
> 
> 
> 
> 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: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] 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" <mistria@xxxxxxxxxx> 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
> My blog - My Tweets 
> 
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev_______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> 
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>