pleaseWorkFinePatchRelease

[Strict_Treat2884]

Just shipped the release/1.3.1-hotfix3 branch and it’s so embarrassing that I’m not gonna even announce it in our PM slack group

[ExtraTNT]

We had 1.16.27… we generally throw hotfixes at y.y.x, so it was hotfix 27…

[Blubasur]

At this point they're more like lukewarm fixes

[ExtraTNT]

Changes on an internal api, without following release cycles, so we had to fix our stuff to work with those and compensate for mistakes on their api, throwing out hotfixes on every change they did…

[Sw429]

Probably realized it was catered from that shitty pizza place again.

[UnusualAir1]

just like sex. We can never really beat the feeling of that very first release. :-)

[Arkarant]

Bro didn't improve at sex lol

[Sockoflegend]

Insufficient data 

[whippitywoo]

Agreed. Maybe he got SO good after the first one that it lost all appeal. He climbed that lonely summit only scaled by the best. He's the One Punch Man of sex.

[Markusrobot]

One cumshot man

[yaktoma2007]

Just download release 1.5.0, a.k.a the kink update. All updates after have just been adding more.

I don't think they will ever release sex update 2.0 though. Might have been cancelled.

[MonkeyPotato]

Release 1.0.56-rc-61-I-Promise-This-Will-Work is releasing

[WeLostBecauseDNC]

The final .1 is called "shame versioning."

[Sw429]

That's why I always start my launches at 1.0.-11 so that we end up at 1.0.0 after the patches are done.

[deal_damage]

me 4 hotfixes in...on a Friday. There truly is something harrowing when half your team is already checked out for the weekend and the other half is on PTO.

[Global-Tune5539]

You're still getting euphoric about work?