Timeline for How to approach long-lived feature code reviews in trunk based development?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 25, 2019 at 7:47 | history | edited | Ewan | CC BY-SA 4.0 |
added 54 characters in body
|
| Apr 24, 2019 at 21:33 | comment | added | Stu | Oh ok, I misunderstood that the 'comment out' part was a stop-gap, because that's the current long-lived solution | |
| Apr 24, 2019 at 21:21 | comment | added | Ewan | i wouldnt recommend it normally, but you have to dig yourself out of the hole before you can start working properly. Its better to merge and comment quickly and simply than try to cherry pick or work out a clever merge strategy | |
| Apr 24, 2019 at 20:04 | comment | added | Stu | So the 'comment out the bits that don't work' part is the part I don't like, if it's a simple feature this works but when the feature spans multiple files in multiple places it's hard to keep track of. Have you run into this problem? | |
| Apr 24, 2019 at 18:41 | history | answered | Ewan | CC BY-SA 4.0 |