DEV Community

Discussion on: Goodbye Master, Hello...What?

Collapse
 
scottshipp profile image
scottshipp

It has to be trunk! If you use the term 'branches' and 'working tree', a lot of order is restored to the universe (in my opinion) by calling the trunk of the tree what it is:

the trunk!

I've been so surprised about this discussion. I can't imagine calling it anything else.

Except . . .

The tide in the community seems to be inevitably toward main . . . and that's what my company has now adopted internally. Oh well.

Collapse
 
codemouse92 profile image
Jason C. McDonald

Actually, I think you make a pretty good point. The only trouble in our system with calling it "trunk" is that we effectively have three trees: stable, fresh, and (now) devel. While changes generally flow devel -> fresh -> stable, that's not always the case. If there's a critical bug in stable, and we're working on a separate release on fresh, we would need to branch off stable, change things, run it through the CI/CD, and then land that branch directly to stable.

It's somewhat along the same lines as when one of our team members said it should really be "main" to indicate "the primary branch" — even he agreed that didn't make sense once I explained that we had three primaries.

Collapse
 
scottshipp profile image
scottshipp

Three trunks . . . It's a hydra! :D

Some comments have been hidden by the post's author - find out more