Stabilization and Release Cycles and Process

[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?

[Fishrock123]

Aligning w/ v8 cycles

see also #490

[Fishrock123]

Website update automation

Doesn't seem like it belongs here?

[mikeal]

Should we close this with a reference to the new issues we decided to create about specific points of contention?

[Fishrock123]

See also #544

[rvagg]

removed tc-agenda label, I don't think this needs to be scheduled again just now although I'm sure there will be more discussion about this