Hacker News Reader

They are not bound to specific dates, as shipping to hit an arbitrary date creates a buggy software.

A version is released when a new feature/a set of features is ready. This is actually the first public release, that's why there are no release dates online.

View on HN

I think you should tie the licence to major versions, and give people confidence that they will still receive updates for bug fixes and patches. But they’ll have to purchase a licence to get new features.

I just feel it's hard to evaluate the price if I don't have a rough idea of how often there might be updates. Is it a monthly thing? Every 4 months? 8? Once a year? I don't know how much time passed between v1.0 and 1.1 and 1.2. I don't even need exact dates. A statement like "We expect to push out a new version every few weeks/months/once a year or so" makes it easier to reason about the cost.

You are right that was updated to free updates for one major version (e.g: license 1.2.0 is also valid for 1.3.0, 1.4.0 but not for 2.0.0).

Thanks for suggestions

Reply on news.ycombinator.com