>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-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] 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" <mist...@redhat.com> 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 cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
