3 ms·

I guess this might work in a pure SaaS environment, but our product has an on-premise version (think Jira data-center), so what keeps us from releasing more oft

• JohnFen 4y ago
  > what keeps us from releasing more often is the maintenance burden that imposes on our customers. You guys rock. Almost no software companies pay any attention to the fact that every new release imposes a burden on their customers, and rapid release schedules impose that burden rapidly. In a way, it's offloading some of the development burden onto your customers. This is true for pure SaaS products as well, although to a lesser degree. I am very happy to hear of a company that remembers this and takes it into consideration.
• gnat 4y ago
  We release new on-prem versions every fortnight and it's up to the customer to decide if they want to upgrade to it or not. We ack the maintenance burden but also that if they want a new shiny then they need to accept that it means an upgrade. Downside, of course, is that different customers have different versions of our software on their premises. Support's job is harder, as they need to know "oh, you're on 2.14 and this is a problem with preorders, that bug was fixed in 2.18" for a bunch of historical versions and problems.