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.
Difference between revisions of "JSDT/Confcalls/Minutes 20160502"
| Line 37: | Line 37: | ||
* GE, CB: We target to RC1, and the team should verify and set version | * GE, CB: We target to RC1, and the team should verify and set version | ||
** 3.8 is for Neon: what is targetted for Target Milestone: RC1 | ** 3.8 is for Neon: what is targetted for Target Milestone: RC1 | ||
| − | ** 3.9 is for Neon.1 | + | ** 3.9 is for Neon.1: the leftover, so what we cannot do for Neon. |
| + | |||
| + | == Going Forward after Neon == | ||
| + | |||
| + | GE: we have until end of June for Neon. What to do with Larger items in Gerrit that are not fitting in Neon? | ||
| + | |||
| + | In previous releases WTP used to have a branch, but now there are not SR1 and SR2 anymore, but Neon.1 and Neon.2 | ||
| + | |||
| + | Having a branch will be a little bit complicated. | ||
| + | Gorkem opened 2 new IPZillas, one is to ship Nodejs runtime. He expects this CQ will take some time, and it might not be ready by Neon.1 | ||
| + | |||
| + | Other things to consider for Neon+n (normally +1 in September, +2 in March) | ||
| + | * Closure Compiler, under CQ | ||
| + | * Typescript Language services (provides a lot of tooling that we're using in JSDT) | ||
| + | * we might replace Esprima | ||
Latest revision as of 10:15, 10 May 2016
Contents
JSDT/Confcalls/Minutes 20160502
Attendees : Ilya, Adalberto, Gorkem, Patrik, Ian, Chuck, Victor S, Orlando,
Quick references: JSDT changes (pending), JSDT Open Bugs
Debugger
Ilya: reviewed and pushed the main Debugger stories. Plus he wants to improve hot-swap, to push source changes directly on running app. The debugger needs to be able to terminate the Nodejs process. See BUG 489041
- Do we want to push the auto-reload for RC1 or it is for Neon.1?
- GE, IB, we could move non-risky stuff to RC1 or RC2, i.e. termination of running Nodejs. Otherwise, it'll be Neon.1
Adalberto prepared a draft for the newsletter, see Nodejs development with JSDT
Gorkem took a look at Electron (http://electron.atom.io/), which has a Nodejs based debugging system. We should take a look and compare functionalities.
ES6
Gorkem noticed ES6 is the component with the major problems at the moment, as it seems the AST is not refreshed to the current state of the file.
For RC1, we'll focus on improve this sync. Based on this improvements we'll decide what to bring in the next rel
Ian fixed the tests, and now the test suite is working again. He's now still working on improving all tests except decorators.
Note: there are some issues related to versioning, Patrik and Ian are going to exchange information to solve these problems
Shane has a big pending change, but this probably should not enter in RC1
Other
Chuck: RC1 continues until May 12
- GE, CB: We target to RC1, and the team should verify and set version
- 3.8 is for Neon: what is targetted for Target Milestone: RC1
- 3.9 is for Neon.1: the leftover, so what we cannot do for Neon.
Going Forward after Neon
GE: we have until end of June for Neon. What to do with Larger items in Gerrit that are not fitting in Neon?
In previous releases WTP used to have a branch, but now there are not SR1 and SR2 anymore, but Neon.1 and Neon.2
Having a branch will be a little bit complicated. Gorkem opened 2 new IPZillas, one is to ship Nodejs runtime. He expects this CQ will take some time, and it might not be ready by Neon.1
Other things to consider for Neon+n (normally +1 in September, +2 in March)
- Closure Compiler, under CQ
- Typescript Language services (provides a lot of tooling that we're using in JSDT)
- we might replace Esprima