-
Notifications
You must be signed in to change notification settings - Fork 630
We announce approved maintenance policy window for Ruby #602
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
Conversation
zzak
commented
Jan 20, 2014
- Update timestamp for merge date
@zzak You should apply @nurse 's comments. https://bugs.ruby-lang.org/issues/9215#note-4 |
@hsbt Thank you, I must have missed the email. |
@hsbt please check it |
@zzak I think you should get confirmation of @unak and @nagachika , and apply additional @nurse 's comments. |
@hsbt I need to apply new comments from naruse and martin, but I haven't had time. |
Added a note to explain responsibility of maintainer, and course of action upon maintainer discharge.
A technical comment: unless the history per se is relevant, it would be easier for the translators/maintainers to have the commits squashed before merge. |
I'm reconsidering the best location for this documentation, And also, it's more of a policy that is on-going, rather than a news related article. With that said, I'm only leaving it open so I don't forget to do something about it. |
Ok! Thanks for your feedback on this one, @zzak. |
I've imported this document to the official ruby wiki, so closing this as its not NEWS worthy. |