Are 65xx builds not releasing to 6.0.2 EAP?

Many issues have been addressed in the 6,5xx builds including ones I want to test but the 6.0.2 EAP releases continue to stay on the 60xx builds. Are the 6,5xx builds not going to be part of 6.0.2?
Thanks,
Jon

11 comments

Hello Jon,

JS> Many issues have been addressed in the 6,5xx builds including ones I
JS> want to test but the 6.0.2 EAP releases continue to stay on the 60xx
JS> builds. Are the 6,5xx builds not going to be part of 6.0.2?

65xx builds are going to become the 6.5 release, and will be released when
the 6.5 EAP starts.

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0

If something is marked as "Fix Version->Demetra Minor Release" but
"Fixed in build->6524" is it in 6.0.2 or 6.5 or both? There are quite a
few bugs like this listed in the release notes link that you gave.

Thanks,
R

0

Hello Robert,

RG> If something is marked as "Fix Version->Demetra Minor Release" but
RG> "Fixed in build->6524" is it in 6.0.2 or 6.5 or both? There are
RG> quite a few bugs like this listed in the release notes link that you
RG> gave.

Bugs marked like this are fixed both in 6.0.2 and 6.5.

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0

For such bugs fixed in both places, how do I know which 6.0.2 build to check since fixed in build only shows 65xx? For example, what 60xx biuld fixes this one: http://www.jetbrains.net/jira/browse/IDEADEV-10628

0

Hello Jon,

JS> For such bugs fixed in both places, how do I know which 6.0.2 build
JS> to check since fixed in build only shows 65xx? For example, what
JS> 60xx biuld fixes this one:
JS> http://www.jetbrains.net/jira/browse/IDEADEV-10628

Unfortunately there is no "hard and fast" way to know, but if the resolution
date of the issue is earlier than the release date of the build, then the
fix is available in the build. This particular issue is fixed in 6077.

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0

Hello Robert,

RG> Ditto http://www.jetbrains.net/jira/browse/IDEADEV-10985
RG> I don't seem to see the fix with build 6077

This one was mistakenly marked as "minor release". I'll correct this now.

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0

.... and there was me thinking you meant you were going to correct
reality to match JIRA by porting the bug ;)

0

Hello Robert,

RG> ... and there was me thinking you meant you were going to correct
RG> reality to match JIRA by porting the bug ;)

This new feature hardly looks like a critical bugfix to me. :)

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0

Hi Dmitry - the original poster who supplied the CPU snapshot has tested the fix of IDEADEV-10628 on 6077 and found the problem still there. Are you sure it was fixed in 6077?
Thanks,
Jon

0

Hello Jon,

The fix itself is in 6077 for sure. If that still slow it means we haven't
fixed anything or at least not what've been actually slow.
Would you please attach a fresh snapshot there or mail me where can I take
it from?

-


Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hi Dmitry - the original poster who supplied the CPU snapshot has
tested the fix of IDEADEV-10628 on 6077 and found the problem still
there. Are you sure it was fixed in 6077?

Thanks,

Jon



0

Please sign in to leave a comment.