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

Change default branch to "main" #1782

Closed
vincepri opened this issue Jul 2, 2020 · 8 comments
Closed

Change default branch to "main" #1782

vincepri opened this issue Jul 2, 2020 · 8 comments
Assignees
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/release-blocking Issues or PRs that need to be closed before the next release lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. wg/naming Categorizes an issue or PR as relevant to WG Naming.
Milestone

Comments

@vincepri
Copy link
Member

vincepri commented Jul 2, 2020

Once the community agrees on the naming, we need to change our default development branch to main, and check that any tools or references to it are changed as well.

This includes the container image tag used in development.

/kind cleanup
/wg naming
/milestone Next

@k8s-ci-robot k8s-ci-robot added this to the Next milestone Jul 2, 2020
@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. wg/naming Categorizes an issue or PR as relevant to WG Naming. labels Jul 2, 2020
@randomvariable randomvariable modified the milestones: Next, v0.6.x Aug 14, 2020
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 12, 2020
@vincepri
Copy link
Member Author

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 12, 2020
@randomvariable randomvariable modified the milestones: v0.6.x, v0.7.0 Mar 11, 2021
@randomvariable
Copy link
Member

Let's do this. We have instructions here https://www.kubernetes.dev/resources/rename/

@randomvariable
Copy link
Member

/kind release-blocking

@k8s-ci-robot
Copy link
Contributor

@randomvariable: The label(s) kind/release-blocking cannot be applied, because the repository doesn't have them.

In response to this:

/kind release-blocking

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.

@randomvariable randomvariable added the kind/release-blocking Issues or PRs that need to be closed before the next release label Apr 15, 2021
@randomvariable
Copy link
Member

/assign
/lifecycle active

@sedefsavas
Copy link
Contributor

This is done.
/close

@k8s-ci-robot
Copy link
Contributor

@sedefsavas: Closing this issue.

In response to this:

This is done.
/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/release-blocking Issues or PRs that need to be closed before the next release lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. wg/naming Categorizes an issue or PR as relevant to WG Naming.
Projects
None yet
Development

No branches or pull requests

5 participants