4 ms·

If only there was no downside, but you can't change 15+ years of convention and not break something in the process. For example, I've had Homebrew upgrade fail

by veeti 3y ago

If only there was no downside, but you can't change 15+ years of convention and not break something in the process. For example, I've had Homebrew upgrade fail because someone thought the "master" branch must not only be renamed but also permanently eradicated from a cask repo, Yocto had the same issue [1], etc. [1] https://github.com/ostreedev/ostree/issues/2360 https://github.com/ostreedev/ostree/issues/2360

bombcar 3y ago
Reddit died for a number of hours because of this, too. https://www.reddit.com/r/RedditEng/comments/11xx5o0/you_broke_reddit_the_piday_outage/ https://www.reddit.com/r/RedditEng/comments/11xx5o0/you_brok... > The nodeSelector and peerSelector for the route reflectors target the label `node-role.kubernetes.io/master`. In the 1.20 series, Kubernetes changed its terminology from “master” to “control-plane.” And in 1.24, they removed references to “master,” even from running clusters. This is the cause of our outage. Kubernetes node labels.
- freedomben 3y ago
  Yep, this has been a constant pain point for me nearly every day. Having dozens of repos I work in across multiple organizations, where half follow the old convention (master) and the other half follow new (main), when I want to switch branches I usually have to do it twice. First `git co main` and if that doesn't work, `git co master`. Vice versa doesn't work because older repos that have been converted have a master branch! It's usually way behind. There are also tons of scripts and CI/CD yaml everywhere that has to be modified for main vs. master. Main is a better name IMHO (increased clarity and brevity) but it is far from "zero downside."
  - bombcar 3y ago
    It should have been built into the client so that if a co of main fails, it tries master. But that would be too easy.

4 ms·

If only there was no downside, but you can't change 15+ years of convention and not break something in the process. For example, I've had Homebrew upgrade fail

by veeti 3y ago

bombcar 3y ago
Reddit died for a number of hours because of this, too. https://www.reddit.com/r/RedditEng/comments/11xx5o0/you_broke_reddit_the_piday_outage/ https://www.reddit.com/r/RedditEng/comments/11xx5o0/you_brok... > The nodeSelector and peerSelector for the route reflectors target the label `node-role.kubernetes.io/master`. In the 1.20 series, Kubernetes changed its terminology from “master” to “control-plane.” And in 1.24, they removed references to “master,” even from running clusters. This is the cause of our outage. Kubernetes node labels.
- freedomben 3y ago
  Yep, this has been a constant pain point for me nearly every day. Having dozens of repos I work in across multiple organizations, where half follow the old convention (master) and the other half follow new (main), when I want to switch branches I usually have to do it twice. First `git co main` and if that doesn't work, `git co master`. Vice versa doesn't work because older repos that have been converted have a master branch! It's usually way behind. There are also tons of scripts and CI/CD yaml everywhere that has to be modified for main vs. master. Main is a better name IMHO (increased clarity and brevity) but it is far from "zero downside."
  - bombcar 3y ago
    It should have been built into the client so that if a co of main fails, it tries master. But that would be too easy.