[countspongebob]

We are doing more than keeping the lights on. Purpose of the public roadmap (which just launched, we'll need some time to really get it right, I'm sure) is to show what we are working on. Any comment on the work around github integration safety as an example?

Watching for feedback here, but it's nice to know when I'm getting reachouts on product feedback directly who is touching base. Linked-in is great for that. But also, if you want to provide feedback we launched the roadmap on github if that's your preference. Trying to cover both kinds of customers.

[aeyes]

You are honestly trying to tell me that a developer-focused company has no better way to get user feedback?

Issue tracker? Idea tracker (check this as an example: https://circleci.canny.io/)? Customer support? Email?

[JimDabell]

> it's nice to know when I'm getting reachouts on product feedback directly who is touching base. Linked-in is great for that.

It’s unclear if you are trying to be ironic here or serious, but in case you are being serious: this kind of language alienates a lot of technical people and reads like a parody. “Reach out” and “touch base” are salesperson lingo clichés that make people cringe, and using “reachouts” as a noun doubles down on that. Nobody here thinks LinkedIn is an appropriate venue for technical feedback (many people can’t stand it at all), and it’s LinkedIn, not Linked-in. I apologise if this comes across as snarky but if you want genuine communication with technical people, talking like a salesperson cliché undermines your goals. What you communicated with this announcement was “Heroku is in maintenance mode, run by non-technical people”. Your comments here are reinforcing that. If you want to connect with technical people, you have to lay off the salesperson lingo and talk like a normal person not InMail spam.

[snowwolf]

My wish list:

* HTTP/2 (3?) (on the roadmap) * a refresh of the dyno line-up - at least pass on some of the cost savings of removing/supporting free tier by reducing dyno pricing or preferably bumping specs * auto-scale for all dyno tiers * rebuild security team with reputable lead * edge / multi region active-active DX * edge ssl termination * iterate on chat ops (underrated feature) * more metrics * more alerting (e.g. crashed apps) * better user/access team management (default app roles) * enhanced secrets management in env (2 layers of env view/roles - config vs secrets) * DDOS protection * Treat CI env vars as secrets!