Announcement

Collapse
No announcement yet.

Git 2.30 Released As More Projects Shift To "Main" As Their Default Branch Name

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Originally posted by bug77 View Post

    Convention over configuration, that's why.

    Also, "master" perfectly describes its role: it's the keeper of vetted versions. "Rolling", "edge" or "dev" are only fitting if you use git like svn and shove all development in the wrong place.

    And there's no hate, just an irritation caused by a seemingly disproportionate amount of effort (and that includes reporting of these changes) going into an otherwise irrelevant direction.
    Except the "keepers of vetted versions" are stable branches or releases. Yes, in good development models the default branch should be always usable (that's actually where I got "rolling" from) or at least somewhat usable (approximately what Linux does, "edge"), and when you see the default branch named "dev", you know someone is not using the full potential of git. Having different names of the default branch for different models can help documenting the development model, and that's why configurability is a good thing. Imagine all projects calling their main executable "a.out" just because that was a convention before make was a thing.

    Comment

    Working...
    X