version control - Git: how to commit and cherry-pick bug fix? -


our development team uses dev branch majority of commits , branch out each month release branches. wondering what's popular model handle bug fix commits. commit head of monthly branch (most recent one, 2015.jun branch) , cherry-pick (or rebase) dev branch? or commit head of dev branch, cherry-pick monthly branch. way better?

according site, says "bugfixes rel.branch may continuously merged dev branch". model? there issues it?

git-flow (your link) or similar workflows quite commonly used. merging release branches develop regularly when bugfixes applied way go imho.

about other points in question

commit head of monthly branch (most recent one, 2015.jun branch) , cherry-pick (or rebase) dev branch?

you cherry-pick them develop wouldn't give explicit "merge", visible in history. rebasing release branch onto develop, you don't want that, develop have recent commits not stable , not related ongoing release. if meant rebase develop onto release - although technically ok avoid not rewrite of history of develop, if there multiple contributors.

or commit head of dev branch, cherry-pick monthly branch. way better?

i don't recommend either. if you're fixing bug going release, it's natural fix "in-place" in release branch, , merge release develop carry fix on (or cherry-pick if don't want merge). doing other way (fixing on develop , cherry-pick on release) doesn't guarantee compatible release.

to summarize point of view, it's best explicit possible. if bugfix in scope of release, apply on branch merge develop, may or may not result in stable codebase.


Comments

Popular posts from this blog

javascript - gulp-nodemon - nodejs restart after file change - Error: listen EADDRINUSE events.js:85 -

Fatal Python error: Py_Initialize: unable to load the file system codec. ImportError: No module named 'encodings' -

javascript - oscilloscope of speaker input stops rendering after a few seconds -