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

Workflow Recommendation - Probably your 1000th

From
Bbradford <fingermark@gmail.com>
Date
Dec 1, 2011, 18:26 UTC
Message-ID
<CAEbKVFSXn3we7Btb3fN5DUW7BMub_ZrBeUwLUZrRFTmESoW97A@mail.gmail.com>

You guys probably receive a ton of workflow related questions. I'm trying to convert from svn to git. In order to complete, I would like to be able to provide a workflow to our team. We typically go from dev -> qa -> production (Java and Rails projects). The problem is that sometimes QA can get backed up and we'll need to release something to production while QA is doing their thing. What is a good workflow? I would like to not use git-flow, because it's another tool. I've read suggestions to use environment branches (master, staging, production). I've also read not to do this and just use master, tagging your production releases. How well would our setup, where things can get backed up, work with the latter? Are there any alternative suggestions?

Thanks, Bradford

Next: Stephen Bash
Message 1 of 4 in “Workflow Recommendation - Probably your 1000th”
  1. bradfordDec 1, 2011
  2. Stephen BashDec 1, 2011
  3. bradfordDec 1, 2011
  4. Stephen BashDec 2, 2011

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.