Skip to content

Stabilization and Release Cycles and Process #405

@mikeal

Description

@mikeal

We need to revisit this subject for the next TC meeting.

  • Release post-mortem (what worked great, what sucked)
  • Aligning w/ v8 cycles
    • Revisit numbering approach to handle breaking changes in an unstable line.
  • Unstable/Stable designations
    • Version number selection process
    • How do we know when we're adopting breaking changes?
  • Logo selection process
    • Need assets in line for next release for the nightlies
  • Website update automation
  • Who can do a release?
  • How often can we push releases?
    • How often do we think is responsible?
    • How close are we automation wise to being able to accomplish our goals.
  • Should we release breaking changes before nan has support?

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