Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

doc: add TSC meeting minutes 2015-07-08 #2184

Closed
wants to merge 0 commits into from

Conversation

rvagg
Copy link
Member

@rvagg rvagg commented Jul 15, 2015

No description provided.

* Michael Dawson: Working on getting PowerPC to build on io.js, tested the security fix from last week, joyent/node triage.
* Steven R Loomis: Worked a bit on the Intl WG, not much else.
* Alexis Campailla: converged CI, almost done. Dealing with windows installer issues. Expect converged CI to work in a week.
* Jeremiah Senkpiel: General triaging and reviewing, helped do the release last friday. _unrefActive with optimizations with heap timers. At CascadiaJS the next of the week to get people’s feedback.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

_unrefActive is throwing off the following formatting

@cjihrig
Copy link
Contributor

cjihrig commented Jul 15, 2015

LGTM with a couple comments

@mscdex mscdex added the doc Issues and PRs related to the documentations. label Jul 15, 2015
* James: It also ties into our regular release schedule and merging next into master etc. The next-to-master merge defines when we can do an LTS release. This should happen at least twice a year. The LTS is cut just before a merge (major bump), so by the time a LTS is cut it should have been stable for half a year.
* James: please kick tires on this proposal, get feedback from the user communities you’re connected to wrt the frequency and release date.
* Rod: the TSC should consider the timeframe, and the requirement that there should be two next-to-master merge yearly.
* Trever: how does this fit with a 6-week release schedule on master?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/Trever/Trevor/

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@bnoordhuis
Copy link
Member

LGTM with nit.


### Present

* Mikeal Rogers -
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does it has a - at the end?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed

rvagg added a commit that referenced this pull request Jul 16, 2015
PR-URL: #2184
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
@rvagg rvagg closed this Jul 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants