JSDT/Confcalls/Minutes 20160510

JSDT/Confcalls/Minutes 20160510

Attendees : Ilya, Victor R., Victor S., Gorkem, Patrik

Quick references: JSDT changes (pending), JSDT Open Bugs

Debugger

Ilya fixed Bug 493160, a debugger issue +1ed by VR and he now is working mainly on documentation. He is also working on Bug 489041: Gulp - kill long running processes. This has issues in windows as the "Gulp" process cannot be killed, because it is still part of the Nodejs process. He'll try to provide a fix until Friday, to see if it enters RC1.

• VR: we have a bug in https://bugs.eclipse.org/bugs/show_bug.cgi?id=439778, is it related to Hotspot ?
• IB: no, it is not coupled with hotspot
• VR: it is an old issue, it is hard to reproduce and the behavior is similar to newer known bugs: breakpoint does not hit under certain conditions.

• GE: Any news on debugger launcher?
• IB: https://bugs.eclipse.org/bugs/show_bug.cgi?id=493234, to reproduce: Install WTP M7, if there is no Chromium, and you start debug, you get an NPE
• IB: I guess it happens when you start nodejs debug session and there is no Chromium, so you'll get this error. Maybe if there is not Chromium feature, it'll fail.
• VR: Chuck suggests to show a dialog if there is no Chromium installed.
• IB: for now I assign it to me, then I'll share with Adalberto
• VR: Will it be possible to launch nodejs application without debugger?
• IB: Yes, running node is independent from debugger.

JSON Editor

Snjezana still working to solve some JSON bugs, as example the preference page will probably go to RC1 + other issues.

Alina is working on this: https://bugs.eclipse.org/bugs/show_bug.cgi?id=491928

Victor created CQ to use icons created by Patrik, and will create another CQ to use material created by Ilya

Ilya: while writing a tutorial on JSON editor I spotted an issue about disabling spellchecker and reported Bug 492972. Is it easy to fix ?

• VR: Not exactly easy. we need to disable the reconcilier, and it can be quite problematic.
• VR: I'm now working on fixing AST.
• GE: we could ask Snjezana to fix this.

ES6

Gorkem: we have a fix for outline supporting export. This export is complex, and we should postpone the fix to the Next release: 3.9 (Neon.1). See: https://bugs.eclipse.org/bugs/show_bug.cgi?id=489656

Shane has finished with another feature that provides model parsing, so we can properly support parsing of model issue. https://bugs.eclipse.org/bugs/show_bug.cgi?id=492130

• GE I would like to have this fixed in Neon - See bug 492130, "[ES6] Define a way to enable module parsing", does it makes sense ?
• VR: Yes, but there are also other issues to address.

JSDT Project Management

• We'll need to create a 3.9 Target Milestone for Neon.1
• We need proper licensing: https://bugs.eclipse.org/bugs/show_bug.cgi?id=493168.

• VR: We need to put proper about.html with proper licensing. There is comment on this about bugzillas. There is some issue about chromium but is described in bug. Anyhow it must point to EPL license.
• GE: i.e. the JSDT.chromium has not the about.html with proper license
• VR: for the legal stuffs, read this: https://eclipse.org/legal/guidetolegaldoc.php#LegalDoc
• IB: Are there differences between chromium and bower licensing?
• GE: you can see the differences in the installation dialog

Patrik: I'll fix Licensing issues in Bug 493168 and in Bug 493166.

• VR: we should try to avoid CQs, as there is no time for this.
• PS: I'll try to keep the changes below 1024 lines, to avoid CQs

Content assist This is unassigned: https://bugs.eclipse.org/bugs/show_bug.cgi?id=489320

• GE: Ian won't take care of these changes anymore

Neon RC

• IB: how we should proceed after friday ?
• GE, VR: RC1 requires one PMC's +1, as example from Victor. After RC1 we need more +1s from PMC
• IB: What if we want to provide fixes after Friday: we will need +1 from Victor and +1 from Chuck. ?
• GE: Yes
• VR: If we find critical issues later, we'll need to ask other PMC's +1-
• IB: I'm wondering, for my components, when is the latest time I can provide changes.
• VR: build usually spins on Friday. Usually no change sent on friday is included in the build, unless re-spin
• IB: when is the last time we can submit a gerrit for an important fix
• GE: until RC4, early june ( but we should try to avoid RC3 and RC4 ..) then there will be the quiet week, then Neon is released on June 22
• IB, VR: the later the change enter, the harder is to have +1s (RC1 : one +1, RC4; four +1 .. )
• VR: this should be testing period, if you see criticals, we should fix them

• PS: see this reference for Platform UI rules in RC1