News for hackers. Stuff that matters.
Re:Trunk-Based Development by crdoconnor on Sunday January 29, 2017 @02:08PM (#13515942)
I've done that. It signalled that the customer had a lack of faith in the stability of our releases.

In our case it was a valid concern (our team had a pretty awful track record).

Re:Trunk-Based Development by brianwawok on Sunday January 29, 2017 @02:44PM (#13516150)
Apparently you have never sold to a fortune 500? Many require bug fixes only of your app for X years. They don't care about new versions. Nothing about faith but about their priority. Using the latest and greatest is not their priority.
Re:Trunk-Based Development by crdoconnor on Sunday January 29, 2017 @02:56PM (#13516218)
We were selling to Fortune 500s.

The upgrade paranoia only kicked in when they were subjected to broken releases and had to roll back.

Re:Trunk-Based Development by devonkim on Sunday January 29, 2017 @03:20PM (#13516349)
The F500 is incredibly varied in their requirements even within the same company. I've seen demand for new features and long term, keep-everything-the-same-as-day-one from the same group for different services / products. Paying more money to keep things from not changing or for not adding features is something unique to enterprise environments though.
Re:Trunk-Based Development by icebraining on Sunday January 29, 2017 @02:47PM (#13516164)
Well, sometimes the lack of stability is purposeful - new features are added, old features are deprecated, etc. How do you deal with that?