Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Kepler SR3 for Java 8?


I was not trying to offend anyone with this statement. If it came across
that way, I apologize.

I do want to point out that when I suggested that presenting this as a
service release was not a necessity (see Kepler J8 variant in the thread),
members of the JDT team still were in opposition, which I read as hesitation
over presenting the released patch as finished release quality. If you look
through the thread, you will see that others took those statements in the
same way. Judging by your reaction, it sounds like we all misread what was
said. That's excellent news as it removes one more objection from the
summary in my last message and would make it that much easier for the
Planning Council to come to a decision.


- Konstantin

-----Original Message-----
From: cross-project-issues-dev-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Stephan
Sent: Friday, March 28, 2014 5:31 AM
To: cross-project-issues-dev@xxxxxxxxxxx
Subject: Re: [cross-project-issues-dev] Kepler SR3 for Java 8?

On 03/28/2014 09:00 AM, Konstantin Komissarchik wrote:
> Several JDT devs on this thread have voiced concern over stability of 
> Java 8 support
 > since it hasn't had time to shake out all the bugs.

I don't know anyone in our team who would say the release on March 18 didn't
have release quality.

Please carefully read, what people are writing!!

The only point that has been argued is that this release does not qualify as
a *service release*, which we still define as a release with only bug fixes,
no new features and hence no new bugs.

And mind you: when JDT devs mention that we might have bugs in a certain
build, that build probably still has higher quality than many other releases
shipped from :)


cross-project-issues-dev mailing list

Back to the top