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

Should we move to a 3 week cadence #173

Closed
MylesBorins opened this issue Dec 26, 2016 · 7 comments
Closed

Should we move to a 3 week cadence #173

MylesBorins opened this issue Dec 26, 2016 · 7 comments

Comments

@MylesBorins
Copy link
Contributor

MylesBorins commented Dec 26, 2016

~~Hey All. There is a meeting scheduled today but I think it makes sense to push it as many participants are off for the holidays. Are people open to pushing the meeting one week and offsetting future meeting accordingly? ~~

I would also like to suggest that we move to a 3 week cadence, I don't feel that we need bi-weekly anymore.

Thoughts?

edit: I was unaware that today was a holiday when I suggested running the meeting today. Due to this and the fact that no one responded we should keep the meeting as next week. I would still like to discuss a 3 week cadence though.

@hutson
Copy link
Contributor

hutson commented Dec 27, 2016

Though I'm not an LTS member, but someone just interested in attending the meetings, I'm fine with delaying yesterday's meeting until next week. Also, I would be fine with out-right canceling it since there will be numerous occasions in the future where this decision will need to be made, and a known, long-term meeting schedule may (in my opinion) have greater benefit than a single meeting.

My only concern with a 3-week cadence, is what impact it will have on reacting to community needs and getting fixes and enhancements into LTS releases promptly. In particular, I have an interest in the SSL cert enhancement. My hope is that it will ship with the next Node release (which I believe is a minor release in January). Then there's the ~2 week "in the wild' period before it can be incorporated into an LTS release. Would a 3-week cadence negatively effect the ability for the LTS group to turn around getting those enhancements into LTS releases?

That's just my input and thoughts on the matter.

@MylesBorins
Copy link
Contributor Author

@hbetts the three week cadence would have no affect on things landing in the community. The only things that require the lts group to discuss are semver minor changes. Those happen fairly infrequently and one meeting is usually enough to handle a multi month backlog.

My personal concern is that there has been so few topics to discuss that we have ended up cancelling meetings, one cancelled meeting means a 4 week gap. A 3 week cadence will likely involve more meetings, as un-intuitive as that is.

@MylesBorins MylesBorins changed the title Push meeting 1 week, potential 3 week cadence Push meeting 1 week, potential 3 week cadence (Not Happening) Jan 2, 2017
@MylesBorins MylesBorins changed the title Push meeting 1 week, potential 3 week cadence (Not Happening) potential 3 week cadence Jan 2, 2017
@mhdawson
Copy link
Member

mhdawson commented Jan 3, 2017

3 weeks makes sense to me. What is the target for the next meeting ? I don't see an issue for yesterday (which was a holiday for us as well).

@MylesBorins
Copy link
Contributor Author

current plan would be next Monday

@mhdawson
Copy link
Member

mhdawson commented Jan 3, 2017

Monday the 9th works for me.

@MylesBorins MylesBorins changed the title potential 3 week cadence Should we move to a 3 week cadence Jan 9, 2017
@mhdawson
Copy link
Member

mhdawson commented Jan 9, 2017

+1

@MylesBorins
Copy link
Contributor Author

It has been decided!

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

No branches or pull requests

3 participants