-
Notifications
You must be signed in to change notification settings - Fork 569
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
Looking for a releaser for the next v10.x #353
Comments
@joyeecheung @BridgeAR would either of you like to prep a release and pair with me on promoting it? |
I'll be up for that. We just have to finish everything before the 14th as I have very limited time that day. Besides that I am fine. |
I can work on that as well but if there is enough time for @BridgeAR I am good with first come first serve :) |
Seems like @rvagg prepares the release because of the security release. |
Sorry to break the flow here. FYI it's entirely possible that we have different people preparing the security releases across release lines, we've done that plenty in the past. However, the overhead of synchronizing multiple people becomes a real pain and my preference would be to just push it all out and wear the late-night cost of that. |
Did the biweekly release cycle stop? |
@nodejs/releasers I will be on holiday until August 20. If we would like to continue with our current biweekly release rate, the next one should be around August 15 and I won't be there for it. Any volunteer?
The text was updated successfully, but these errors were encountered: