Skip to content

Node.js Foundation Release WorkGroup Meeting 2019-01-17 #407

Description

@mhdawson

Time

UTC Thu 17-Jan-2019 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Thu 17-Jan-2019 08:00 (08:00 AM)
US / Mountain Thu 17-Jan-2019 09:00 (09:00 AM)
US / Central Thu 17-Jan-2019 10:00 (10:00 AM)
US / Eastern Thu 17-Jan-2019 11:00 (11:00 AM)
London Thu 17-Jan-2019 16:00 (04:00 PM)
Amsterdam Thu 17-Jan-2019 17:00 (05:00 PM)
Moscow Thu 17-Jan-2019 19:00 (07:00 PM)
Chennai Thu 17-Jan-2019 21:30 (09:30 PM)
Hangzhou Fri 18-Jan-2019 00:00 (12:00 AM)
Tokyo Fri 18-Jan-2019 01:00 (01:00 AM)
Sydney Fri 18-Jan-2019 03:00 (03:00 AM)

Or in your local time:

Links

Agenda

Extracted from Release-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/Release

  • Additional semver minor to 8.x during maintenance #405
  • Changes to 10.x q1 release schedule #404
  • Plan for Node.js 11 Current releases #397
  • Bringing back regular meetings #333

Invited

  • Release team: @nodejs/Release
  • LTS team: @nodejs/lts

Observers/Guests

Notes

The agenda comes from issues labelled with Release-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Activity

  1. self-assigned this
    on Jan 15, 2019
  2. targos commented on Jan 15, 2019

    @targos
    Member

    I hope I can make it but I have a work meeting 2 hours before and I don't know how long it will be

  3. MylesBorins commented on Jan 17, 2019

    @MylesBorins
    Contributor
  4. richardlau commented on Jan 18, 2019

    @richardlau
    Member

    Does the meeting generator allow for more than one agenda label? There was one lts-agenda labelled item over in nodejs/node that probably should be discussed in these meetings: https://github.com/nodejs/node/labels/lts-agenda

  5. MylesBorins commented on Jan 21, 2019

    @MylesBorins
    Contributor
  6. mhdawson commented on Jan 21, 2019

    @mhdawson
    MemberAuthor

    Agreed, best to just remove lts-agenda and use release-agenda. The tool only allows one label.

  7. richardlau commented on Jan 21, 2019

    @richardlau
    Member

    Agreed, best to just remove lts-agenda and use release-agenda. The tool only allows one label.

    I've added Release-agenda to the issue and removed the lts-agenda label completely (so it doesn't get added to any issues in the future).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

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