We announce approved maintenance policy window for Ruby #602

Closed
wants to merge 11 commits into
from

Conversation

4 participants
@zzak
Member

zzak commented Jan 20, 2014

  • Update timestamp for merge date
@hsbt

This comment has been minimized.

Show comment Hide comment
@hsbt

hsbt Jan 20, 2014

Member
Member

hsbt commented Jan 20, 2014

@zzak

This comment has been minimized.

Show comment Hide comment
@zzak

zzak Jan 20, 2014

Member

@hsbt Thank you, I must have missed the email.

Member

zzak commented Jan 20, 2014

@hsbt Thank you, I must have missed the email.

@zzak

This comment has been minimized.

Show comment Hide comment
@zzak

zzak Jan 20, 2014

Member

@hsbt please check it

Member

zzak commented Jan 20, 2014

@hsbt please check it

@hsbt

This comment has been minimized.

Show comment Hide comment
@hsbt

hsbt Jan 28, 2014

Member

@zzak I think you should get confirmation of @unak and @nagachika , and apply additional @nurse 's comments.

Member

hsbt commented Jan 28, 2014

@zzak I think you should get confirmation of @unak and @nagachika , and apply additional @nurse 's comments.

@zzak

This comment has been minimized.

Show comment Hide comment
@zzak

zzak Jan 28, 2014

Member

@hsbt I need to apply new comments from naruse and martin, but I haven't had time.

Member

zzak commented Jan 28, 2014

@hsbt I need to apply new comments from naruse and martin, but I haven't had time.

@stomar

This comment has been minimized.

Show comment Hide comment
@stomar

stomar Feb 3, 2014

Member

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.

Member

stomar commented Feb 3, 2014

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.

@chikamichi

This comment has been minimized.

Show comment Hide comment
@chikamichi

chikamichi May 31, 2014

Member

@zzak @stomar I agree: git rebase -i once the PR is ready.

Member

chikamichi commented May 31, 2014

@zzak @stomar I agree: git rebase -i once the PR is ready.

@zzak

This comment has been minimized.

Show comment Hide comment
@zzak

zzak May 31, 2014

Member

I'm reconsidering the best location for this documentation,
a blog post is not ideal because many committers dont have access to the file.

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.

Member

zzak commented May 31, 2014

I'm reconsidering the best location for this documentation,
a blog post is not ideal because many committers dont have access to the file.

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.

@chikamichi

This comment has been minimized.

Show comment Hide comment
@chikamichi

chikamichi May 31, 2014

Member

Ok! Thanks for your feedback on this one, @zzak.

Member

chikamichi commented May 31, 2014

Ok! Thanks for your feedback on this one, @zzak.

@zzak

This comment has been minimized.

Show comment Hide comment
@zzak

zzak Jun 14, 2014

Member

I've imported this document to the official ruby wiki, so closing this as its not NEWS worthy.

Member

zzak commented Jun 14, 2014

I've imported this document to the official ruby wiki, so closing this as its not NEWS worthy.

@zzak zzak closed this Jun 14, 2014

@zzak zzak deleted the zzak:future_release_policy branch Jun 14, 2014

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