Timeline for Git Flow best practice for quarantine snapshot to staging environments (dev, test, prod)?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 10, 2024 at 15:56 | vote | accept | Theo5423324 | ||
| Apr 10, 2024 at 8:53 | comment | added | TheFogger | @Theo5423324 Sorry, I don‘t understand what a fixed release date has to do with it. On the date of the release, take the most recent snapshot that has passed qa and deploy it to prod. What I am getting at is that git flow might not be a good fit for you. | |
| Apr 10, 2024 at 7:10 | history | edited | Theo5423324 | CC BY-SA 4.0 | typo |
| Apr 10, 2024 at 7:08 | comment | added | Theo5423324 | @TheFogger because we release on fixed release dates | |
| Apr 10, 2024 at 6:38 | comment | added | Ben Cottrell | "Deploying snapshots to test doesn't really make sense, because after a successful test by QA, someone could commit a change" -- I don't understand this sentence; if someone commits a change, then the snapshot remains unchanged, the new commit results in a different snapshot; any new bug will not be present in the existing snapshot - Snapshots are immutable. | |
| Apr 10, 2024 at 4:33 | comment | added | TheFogger | If qa has already tested a snapshot, why don‘t you just deploy that same snapshot to prod? You can tag the commit where the snapshot was taken from if you want to know which source version is currently deployed. | |
| Apr 9, 2024 at 21:54 | answer | added | Ewan | timeline score: 4 | |
| Apr 9, 2024 at 21:22 | review | Close votes | |||
| Apr 23, 2024 at 3:08 | |||||
| Apr 9, 2024 at 21:15 | history | edited | Theo5423324 | CC BY-SA 4.0 | added 45 characters in body |
| S Apr 9, 2024 at 20:45 | review | First questions | |||
| Apr 10, 2024 at 7:18 | |||||
| S Apr 9, 2024 at 20:45 | history | asked | Theo5423324 | CC BY-SA 4.0 |