git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Hotfix Branching Strategy

From
RGRoman Gelfand <rgelfand2@gmail.com>
Date
Feb 12, 2019, 05:21 UTC
Message-ID
<CAJbW+rkn7wbRhDvRTtdp1aF5wd5PWHu9DqvPFm-BdVkR02Wgvg@mail.gmail.com>
 At any one time, up to 3 developers could be developing hotfixes
addressing issues.    Whether it is one or multiple people working on
hotfixes, we always want to produce one hotfix.  Each hotfix is a
cumulative update since beginning of release.  Just about every hotfix
requires database upgrade.  Being that it is cumulative each developer
is dependent on the other.  Considering the requirements, what should
be a strategy to deal with this problem.?
Thanks in advance
Next: Ævar Arnfjörð Bjarmason
Message 1 of 2 in “Hotfix Branching Strategy”
  1. Roman GelfandFeb 12, 2019
  2. Ævar Arnfjörð BjarmasonFeb 12, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.