Cutting a release (and publishing) does cost significant time and effort. You effectively need to code-freeze, get all code merged into main, run all tests and QA, fix any breaking bugs, compete signoffs etc. On some of our small projects, doing a release could burn up to 2 weeks of real time, which on a monthly release cycle was killing us.
So I can almost buy their reasoning. But otherwise, agree that they can’t be trusted, and releasing once a quarter doesnt seem that hard.
Of course. Although I can kinda see why they dont want to do that either. All the fly-by-night OEMs would be using dev and shipping half-baked ROMs (which I guess they do anyway, but it would be worse).
Cutting a release (and publishing) does cost significant time and effort. You effectively need to code-freeze, get all code merged into main, run all tests and QA, fix any breaking bugs, compete signoffs etc. On some of our small projects, doing a release could burn up to 2 weeks of real time, which on a monthly release cycle was killing us.
So I can almost buy their reasoning. But otherwise, agree that they can’t be trusted, and releasing once a quarter doesnt seem that hard.
You could just have less releases but still develop everything openly…
Of course. Although I can kinda see why they dont want to do that either. All the fly-by-night OEMs would be using dev and shipping half-baked ROMs (which I guess they do anyway, but it would be worse).