Skip to content

Incorrect start date in schedule.json #361

Closed
DerekNonGeneric/wg-nodejs-release
#6

Description

@bnb

The schedule.json file asserts that Node.js v10 is LTS today. As far as I know (?), this isn’t the case.

Historically it seems we trend more toward the end of the month. If truly incorrect, would it be acceptable/more accurate to update it to the 31st and adjust down if needed? Happy to create a PR if the answer is yes.

For what it’s worth, I discovered this last night while working on node-release-lines, which uses the data from schedule.json rather heavily.

Activity

  1. mhdawson commented on Oct 1, 2018

    @mhdawson
    Member

    @jasnell, @MylesBorins can you two comment if we have a specific date to update it to yet?

  2. MylesBorins commented on Oct 1, 2018

    @MylesBorins
    Contributor

    We hadn't picked a date yet. How about Tuesday October 30th?

  3. added a commit that references this issue on Oct 1, 2018
  4. dege88 commented on Oct 2, 2018

    @dege88
  5. added a commit that references this issue on Oct 10, 2018
  6. added a commit that references this issue on Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions