Skip to content

Stabilization and Release Cycles and Process #405

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom
Closed
mikeal opened this issue Jan 14, 2015 · 5 comments
Closed

Stabilization and Release Cycles and Process #405

mikeal opened this issue Jan 14, 2015 · 5 comments

Comments

@mikeal
Copy link
Contributor

mikeal commented Jan 14, 2015

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?
@mikeal mikeal mentioned this issue Jan 14, 2015
Closed
@Fishrock123
Copy link
Contributor

Aligning w/ v8 cycles

see also #490

@Fishrock123
Copy link
Contributor

Website update automation

Doesn't seem like it belongs here?

This was referenced Jan 19, 2015
Closed
Closed
@mikeal
Copy link
Contributor Author

mikeal commented Jan 22, 2015

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

@Fishrock123
Copy link
Contributor

See also #544

@rvagg rvagg mentioned this issue Jan 23, 2015
Closed
@rvagg rvagg removed the tc-agenda label Feb 3, 2015
@rvagg
Copy link
Member

rvagg commented Feb 3, 2015

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

@rvagg rvagg closed this as completed Feb 3, 2015
This was referenced Mar 7, 2020
Open
Open
Open
Open
Open
Open
This was referenced Oct 4, 2022
Open
Open
This was referenced Oct 25, 2022
Open
Open
@snyk-bot snyk-bot mentioned this issue Nov 1, 2022
Open
This was referenced Jan 21, 2023
Open
Open
Open
This was referenced Feb 14, 2023
Open
Merged
This was referenced Mar 15, 2023
Open
Open
@snyk-bot snyk-bot mentioned this issue May 12, 2023
Open
@ashly1111111 ashly1111111 mentioned this issue May 13, 2023
Open
@NOUIY NOUIY mentioned this issue May 13, 2023
Open
This was referenced May 18, 2023
Open
Open
@ashly1111111 ashly1111111 mentioned this issue May 18, 2023
Open
This was referenced May 19, 2023
Open
Open
Open
@ashly1111111 ashly1111111 mentioned this issue May 24, 2023
Open
This was referenced Jun 3, 2023
Open
Open
Open
Open
@NOUIY NOUIY mentioned this issue Jun 15, 2023
Open
@ashly1111111 ashly1111111 mentioned this issue Jun 16, 2023
Open
This was referenced Jul 7, 2023
Open
Open
@ashly1111111 ashly1111111 mentioned this issue Jul 13, 2023
Open
This was referenced Jul 14, 2023
Open
Open
@ashly1111111 ashly1111111 mentioned this issue Jul 17, 2023
Open
@ashly1111111 ashly1111111 mentioned this issue Jul 25, 2023
Open
@NOUIY NOUIY mentioned this issue Jul 26, 2023
Open
@NOUIY NOUIY mentioned this issue Aug 20, 2023
Open
@ashly1111111 ashly1111111 mentioned this issue Aug 21, 2023
Open
@JCsomeShots JCsomeShots mentioned this issue Sep 19, 2023
Open
@kingjay66 kingjay66 mentioned this issue Oct 15, 2023
Open
@leonardoadame leonardoadame mentioned this issue Nov 30, 2023
Open
@jefeaguila jefeaguila mentioned this issue Feb 11, 2024
Open
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mikeal @rvagg @Fishrock123