3 ms·
Sorry, I don't quite get where you're coming from. In nvie's system, you just create a release branch from develop and then merge it back into master and devel
by choult 13y ago
Sorry, I don't quite get where you're coming from.
In nvie's system, you just create a release branch from develop and then merge it back into master and develop when done. There's no other skill other than basic git-fu to do that. You can keep develop up to date with any changes from release branch periodically.
The real complication with releasing is release management. But that's nothing to do with branches or even basic use of git, but one of engineering process in general. There's definitely no magic bullet for that.
- geocar 13y ago> The real complication with releasing is release management. The real complication is developers that think "releasing" is somehow different than "development". When it's in master, then it's released. Whether you call that branch something else, or you use something other than a branch to indicate what is released, is completely irrelevant. The fiction that "develop" is some future point for master causes huge delays at best for large projects. In reality, "develop" is the hope or belief in some magic moment when the software is "good enough", and since it's someone else's job to decide whether it's "good enough", the buck is passed.
- JanezStupar 13y agoI have no idea what your actual argument is. Whatever your problems are they have nothing to do with this particular git branching model. I suspect you have an issue within the culture you are a part of and no git branching model can fix that.