Timeline for When creating a fix, how does branching off the release candidate branch compare with cherry-picking from master?
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 28, 2023 at 19:25 | vote | accept | voobaroo | ||
| Oct 28, 2021 at 3:01 | history | tweeted | twitter.com/StackSoftEng/status/1453557418315632646 | ||
| Oct 23, 2021 at 17:02 | history | became hot network question | |||
| Oct 23, 2021 at 12:25 | review | Close votes | |||
| Oct 28, 2021 at 3:02 | |||||
| Oct 23, 2021 at 10:21 | history | edited | voobaroo | CC BY-SA 4.0 |
fix description
|
| Oct 23, 2021 at 10:19 | comment | added | voobaroo | @jonrsharpe I made a mistake in the title -- I meant to say "cherry-pick from master" (i.e. trunk-based development) rather than doing a regular merge from master into the RC. I updated the title and description. | |
| Oct 23, 2021 at 10:18 | history | edited | voobaroo | CC BY-SA 4.0 |
fix title; add clarifying text
|
| Oct 23, 2021 at 10:16 | answer | added | amon | timeline score: 8 | |
| Oct 23, 2021 at 9:55 | answer | added | Doc Brown | timeline score: 3 | |
| Oct 23, 2021 at 9:52 | comment | added | jonrsharpe | Imagine the problem is found after merge1. If you branch the hotfix from master, you won't be able to merge it into release/1.0 without bringing feature/001 with it. | |
| S Oct 23, 2021 at 9:02 | review | First questions | |||
| Oct 23, 2021 at 10:21 | |||||
| S Oct 23, 2021 at 9:02 | history | asked | voobaroo | CC BY-SA 4.0 |