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

stable as subset of develop

From
BPBrett Porter <porter@devrts.com>
Date
Aug 27, 2016, 02:29 UTC
Message-ID
<57C0FB1D.9070206@devrts.com>

In a small group, develop is the branch where all fixes/additions/... from topic branches are merged rather dynamically. Thorough testing of commits may lag behind, but when we think one is a pretty good commit we want to identify it as (at least relatively) the latest stable. We could tag it, but we would like these stable commits to be a branch in the sense that each commit points back to a previous commit.

Merging from a development branch commit to stable isn't quite what we want. It seems more like:

   checkout the new good development commit
   change HEAD to the head of the stable branch
   git add --all
   git commit
   (maybe tag the new commit with the hash of the chosen development commit)

Will that work (one thing beyond my current understanding is if there are index complications)? Other ideas?

This could help with applying successively more intense testing over time and chase down where problems arose.

Next: Jakub Narębski
Message 1 of 4 in “stable as subset of develop”
  1. Brett PorterAug 27, 2016
  2. Jakub NarębskiAug 27, 2016
  3. Brett PorterAug 27, 2016
  4. Jakub NarębskiAug 27, 2016

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.