this post was submitted on 03 Mar 2024
1090 points (97.8% liked)

Programmer Humor

19817 readers
562 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] dan@upvote.au 10 points 9 months ago* (last edited 9 months ago) (1 children)

Our changes land in main at my workplace, once they've received a code review and all CI checks pass (which includes tests, E2E tests, etc). We use feature flags rather than feature branches, so all diffs / pull requests are against main. We use continuous deployment which means changes are automatically deployed once landed. Changes roll out just to employees, then to servers used by a small percentage of users (2% I think), then everywhere. All risky changes are gated by feature flags so they can be enabled or disabled without a code push.

[โ€“] nilloc@discuss.tchncs.de 3 points 9 months ago

We did a similar way with tag based releases, first a test tag, the production tag when signed off.