Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "JSDT/Confcalls/Minutes 20151110"

 
(One intermediate revision by the same user not shown)
Line 22: Line 22:
 
  Orlando Rincon
 
  Orlando Rincon
 
  Victor
 
  Victor
 +
Doug Schaffer
  
 
== Meeting Minutes ==
 
== Meeting Minutes ==
Line 34: Line 35:
 
## More work ongoing to avoid virtual projects
 
## More work ongoing to avoid virtual projects
 
## CQ process to be started to include in JSDT
 
## CQ process to be started to include in JSDT
 +
# We will consider deprecation and removal per API but as a general rule deprecation on Neon release with an option to remove on Neon+1 is acceptable
 +
# Agreed to have to workspace compatability
 +
# Agreed that it will be possible to drop features on Neon release
 +
# No final decision on parser strategy. The two favored choices are acorn or shift-java. We will learn more about Shift before reaching a decision
 +
# Agreed to move validation to extension points

Latest revision as of 14:21, 10 November 2015

Logistics

See JSDT/Confcalls

Meeting Agenda

  1. Updates on current work
    1. JSON Editor
    2. npm and bower contribution
    3. JavaScript Debugger
      1. See the demos for node.js and webkit
      2. Can we start moving the code to eclipse foundation?
    4. Review and discuss conclude proposals for changes on JSDT/JSDTRenewalArchitecture

Attendees

Gorkem Ercan
Adalberto
Alexey Kazakov
Alina
Chuck Bridgham
Denis Golovin
Ilya Buziuk
Mickael
Orlando Rincon
Victor
Doug Schaffer

Meeting Minutes

  1. npm and bower contribution process started
    1. CQ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=481828
  2. JSON Editor
    1. CQ changed to under review
    2. targeting M2 with this contribution
  3. Debugger
    1. Repo with changes https://github.com/jbosstools/chromedevtools
    2. Still needs to be updated to work with JDST breakpoints
    3. More work ongoing to avoid virtual projects
    4. CQ process to be started to include in JSDT
  4. We will consider deprecation and removal per API but as a general rule deprecation on Neon release with an option to remove on Neon+1 is acceptable
  5. Agreed to have to workspace compatability
  6. Agreed that it will be possible to drop features on Neon release
  7. No final decision on parser strategy. The two favored choices are acorn or shift-java. We will learn more about Shift before reaching a decision
  8. Agreed to move validation to extension points

Back to the top