Comments (22)
There is some additional guidance on https://github.com/github/renaming suggesting that if we wait a little bit, GitHub will provide better tools to make the transition go more smoothly.
from metal3-docs.
This could be tried on a repo that is not much used, such as IPAM ?
from metal3-docs.
It would be good to handle the branch renaming in all of our repos quickly to minimize disruption. I imagine a couple of us with admin privileges could go through and do that. Does the k8s community have a set of instructions worked out?
What other changes would we need to make? Does CI need to be reconfigured at the same time?
from metal3-docs.
It's a questionable move by Github and others in my opinion, changing terminology will not have the desired affect, at all. These are problems of perception and human behaviors, not words. It will only cause software breakage all over the place, adding to the already humongous mess of terminology that has already been in place since forever.
However, the proposed changes look reasonable. So, LGTM. +1
from metal3-docs.
This is also a work in progress on the K8S side. They are starting a work group on this AFAIK. so no instructions yet. The prow config has quite some references to master, especially for container images. They'll need to be changed once all the new images are created. We will also need to change all container images references in all repos (in hack and deploy/config folders).
Jenkins will also need to be reconfigured, that's something that we will take care of when the branch change is done.
I would propose to proceed the following way for the branch renaming :
- create the
main
branch in all repositories - modify all references to master, in CI and in all repos, specifically for container images
- modify the default branch
- Fix CI and Jenkins
- remove master branch
from metal3-docs.
We may also need to follow the instructions for setting the new default branch. https://docs.github.com/en/github/administering-a-repository/setting-the-default-branch
from metal3-docs.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from metal3-docs.
/remove-lifecycle stale
from metal3-docs.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from metal3-docs.
/remove-lifecycle stale
from metal3-docs.
It seems that Github has made it easy now to rename the existing branch: https://github.com/github/renaming. Based on that document, the list of the things that will be taken care by Github while renaming is:
- Re-target any open pull requests
- Update any draft releases based on the branch
- Move any branch protection rules that explicitly reference the old name
- Update the branch used to build GitHub Pages, if applicable
- Show a notice to repository contributors, maintainers, and admins on the repository homepage with instructions to update local copies of the repository
- Show a notice to contributors who git push to the old branch
- Redirect web requests for the old branch name to the new branch name
- Return a "Moved Permanently" response in API requests for the old branch name
from metal3-docs.
ref: https://www.kubernetes.dev/resources/rename/
from metal3-docs.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from metal3-docs.
/remove-lifecycle stale
from metal3-docs.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from metal3-docs.
/remove-lifecycle stale
from metal3-docs.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from metal3-docs.
/lifecycle active
from metal3-docs.
/triage accepted
from metal3-docs.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from metal3-docs.
Stale issues close after 30d of inactivity. Reopen the issue with /reopen
. Mark the issue as fresh with /remove-lifecycle stale
.
/close
from metal3-docs.
@metal3-io-bot: Closing this issue.
In response to this:
Stale issues close after 30d of inactivity. Reopen the issue with
/reopen
. Mark the issue as fresh with/remove-lifecycle stale
./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.
from metal3-docs.
Related Issues (20)
- Feature: Add a resource to request the execution of a workload on a BareMetalHost HOT 13
- Go through the quick-start and fix/improve things you find HOT 4
- Document Metal3Cluster HOT 4
- Document Metal3Machine and Metal3MachineTemplate HOT 5
- Document Metal3Data and Metal3DataTemplate HOT 5
- Add cover pages for feature sections HOT 3
- Document IP reuse HOT 5
- Document user-data, meta-data and network-data usage with BareMetalHosts HOT 4
- Add API reference HOT 7
- Document unhealthy annotation HOT 5
- Running custom IPA in an environment where thereis no DHCP - preprovisioning image HOT 3
- Troubleshooting guide HOT 2
- Fix dead links at bmc-events.md HOT 3
- Fix dead links at kubebuilder-migration.md HOT 3
- Fix dead links at nodes-machines-and-hosts.md HOT 3
- Fix dead links at capm3-remediation-controller-proposal.md HOT 6
- Fix dead links at foundation-proposal.md HOT 4
- Fix dead links at managing-reviewers.md HOT 3
- Fix dead links at triage.md HOT 8
- Fix dead links at crs_reference.md HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from metal3-docs.