2 ms·
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
by crdoconnor 10y ago
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).
- brianwawok 10y agoApparently 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.
- crdoconnor 10y agoWe were selling to Fortune 500s. The upgrade paranoia only kicked in when they were subjected to broken releases and had to roll back.
- devonkim 10y agoThe 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.
- icebraining 10y agoWell, sometimes the lack of stability is purposeful - new features are added, old features are deprecated, etc. How do you deal with that?