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

Workflow Help

From
QTQuilkey, Tony <trq@thorpesystems.com>
Date
May 21, 2013, 00:59 UTC
Message-ID
<CAMATmi3bU7hrD-YLY1iVXbekxOx_XZfZ5yYNBfzV_VFSc_W5jw@mail.gmail.com>
Hi,

I am looking at formulating and then documenting our vcs workflow using Git at work. I have an idea of how I want things to work, but am a little hazy on some of the details.

Our basic workflow will be based around: http://nvie.com/posts/a-successful-git-branching-model, with a few exceptions.

We would like to create our release-* branches from the last release tag. From there, we would like the ability to cherry pick (or take the complete diff) commits from the develop branch.

So, we are after is:
1) Create topic (feature) branches from develop, and merge back into
develop when complete.
2) Once it is decided we are packaging a release, make a release-*
branch from the previous release tag.
3) Cherry pick/merge/whatever any commits we want from develop into
the new release-* until it is complete.
4) Merge the new release-* branch into master and tag it.
Repeat as necessary.

At the moment I am a little stuck on how exactly we can cherry pick stuff from develop into a release-* branch. I'm not even sure this approach is exactly what we should be doing.

Our main concern is that at this stage, there is no guarantee that all commits within develop can be pulled into a release.

In regards to how we can achieve the above results any input would be much appreciated. Or if there are any other better options available, I'm all ears.

Thanks,
Tony Quilkey
Next: John Keeping
Message 1 of 4 in “Workflow Help”
  1. Quilkey, TonyMay 21, 2013
  2. John KeepingMay 21, 2013
  3. Magnus BäckMay 21, 2013
  4. Andreas EricssonMay 21, 2013

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.