Similar to what we did with release-1.12 to release-1.14. I would like that we can do something similar after release-1.15 rollout.
Relates to #13745
/cc @kubernetes/sig-docs-zh-owners @kubernetes/sig-docs-zh-reviews
/cc @zacharysarah
/language zh
/priority important-longterm
/s/release-1.15/release-1.16
/s/release-1.14/release-1.15
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
looks like it's time to stop using release-x.y branches as the base branch.
tengqm 11:59 AM
during 1.17 release window, the Chinese localization has been a headache for the release team.
we had a lot of commits directly merged into release-1.16 and only release-1.16 branch
when the release team rebase things back to release-1.16 branch, they saw a lot of conflicts
going forward, maybe we should commit things to master directly since we are kinda catching up with the master branch
idealhack 1:40 PM
agreed, PR to master or a -dev branch
https://kubernetes.slack.com/archives/CE3LNFYJ1/p1575946765043800
Since we're changing the process a little, @chenrui333 or @tengqm can you please add /cc @kubernetes/sig-docs-en-owners on the next switch to master or dev-x.xx? It will help keep everyone in sync!
Thanks @idealhack and @tengqm!
/remove-lifecycle stale
Sure, @jimangel, will keep an eye on it.
cc @kubernetes/sig-docs-zh-owners @kubernetes/sig-docs-zh-reviews ^^^^
this issue is old . can we close this?
/cc @chenrui333
pretty old issue. irrelevant now.
/close
@tengqm: Closing this issue.
In response to this:
pretty old issue. irrelevant now.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Thanks @tengqm!
Most helpful comment
looks like it's time to stop using
release-x.ybranches as the base branch.https://kubernetes.slack.com/archives/CE3LNFYJ1/p1575946765043800