Seems a strange and complicated soution for a simple communication problem. So you are willing to talk with collegues about howto's for development environments and create extra config files and clear, clean and remove code, which seems to need a lot of discipline instead of clear agreements in the daily or weekly scrums? I am not convinced.
To avoid merge problems, you can also make your pull requests smaller, but instead you ban branches altogether.
i think this is the wrong approach, especially when you have to complicate it with features.
nevertheless i liked the talk.
Comments
Comments are closed.
Cool.
Interesting but complicated!
Seems a strange and complicated soution for a simple communication problem. So you are willing to talk with collegues about howto's for development environments and create extra config files and clear, clean and remove code, which seems to need a lot of discipline instead of clear agreements in the daily or weekly scrums? I am not convinced.
nice talk that explains the benefits and downsides of trunk based development. not sure if I'm convinced but it was a good talk.
To avoid merge problems, you can also make your pull requests smaller, but instead you ban branches altogether.
i think this is the wrong approach, especially when you have to complicate it with features.
nevertheless i liked the talk.
Clearly explained another point of view on version control structure. Good presentation skills.
Very good talk.
I think the successfully usage will depend on the concrete project, but because of this talk i now have some ideas to avoid merging problems.
Well given presentation and good to follow. Always good to see another way of working :)