3 ms·
I found this for you: https://trunkbaseddevelopment.com/ https://trunkbaseddevelopment.com/ I only scanned through it, but it seems similar to the de facto wa
by afpx 8y ago
I found this for you:
https://trunkbaseddevelopment.com/ https://trunkbaseddevelopment.com/
I only scanned through it, but it seems similar to the de facto way of doing things before distributed version control systems became popular (in the late 2000s?).
- weinzierl 8y agoI know about this and it doesn't answer my question. This was in part my motivation to post this question here.
- ownagefool 8y agoI think you mistunderstood that link is arguing for. It's basically github flow with tagging on what you release, only goes into a bit more details and discussed alternatives and suffers a "bit from too much information" https://guides.github.com/introduction/flow/ https://guides.github.com/introduction/flow/ Is a cleaner and more obvious guide. The idea is you have a constantly usable master, and your branches should be short lived so you don't hit a brick wall trying to get reviews and merge on your massive change sets. Ultimately it means you want to test and review your change before it goes into master as opposed to creating "production", "staging" and "develop" branches, which largely just kick the can down the road and is a different way to solve that "what's deployed where" issue.
- afpx 8y agoThanks - I should have read through it more.