TSC meeting 24-May-2018

[eslint-deprecated]

Time

UTC Thu 24-May-2018 20:00:

• Los Angeles: Thu 24-May-2018 13:00
• Chicago: Thu 24-May-2018 15:00
• New York: Thu 24-May-2018 16:00
• Madrid: Thu 24-May-2018 22:00
• Moscow: Thu 24-May-2018 23:00
• Tokyo: Fri 25-May-2018 05:00
• Sydney: Fri 25-May-2018 06:00

Location

https://gitter.im/eslint/tsc-meetings

Agenda

Extracted from:

• Issues and pull requests from the ESLint organization with the "tsc agenda" label
• Comments on this issue

Invited

• Nicholas C. Zakas (@nzakas) - TSC
• alberto (@alberto) - TSC
• Kevin Partington (@platinumazure) - TSC
• Ilya Volodin (@ilyavolodin) - TSC
• Brandon Mills (@btmills) - TSC
• Toru Nagashima (@mysticatea) - TSC
• Gyandeep Singh (@gyandeeps) - TSC
• Kai Cataldo (@kaicataldo) - TSC
• Teddy Katz (@not-an-aardvark) - TSC

Public participation

Anyone is welcome to attend the meeting as observers. We ask that you refrain from interrupting the meeting once it begins and only participate if invited to do so.

[not-an-aardvark]

Agenda item: I think we should decide on a schedule for the stable v5.0 release. We've already received 3 requests to backport changes that have landed on master (1, 2, 3), so the delay in putting these changes from master into a release is having an impact on our users.

Ideally, I think we should do a release candidate this week, and then (assuming there are no major bugs) do a stable release on the next cycle.

[platinumazure]

@eslint/eslint-tsc Did we not have this TSC meeting? Or did we not draw up notes? It looks like this issue was closed by the 2018-06-07 meeting notes, hence why the next issue says 2018-06-07 instead of 2018-06-21.

[not-an-aardvark]

The 2018-05-24 meeting was cancelled due to a lack of quorum, but we forgot to close this issue, so we used it as an agenda for the 2018-06-07 meeting. If we close the next meeting issue then the bot will create another meeting issue for the correct date.