On 18.08.2016 22:12, Josh Berkus wrote:
On 08/18/2016 02:24 AM, Stef Walter wrote:
> Yesterday several of us (roughly the top contributors [1] to Cockpit)
> discussed removing the '0.x' from the Cockpit version number.
>
> The plan is from here on out to just go with integer versions, starting
> with version '118' following version '0.117'.
>
> Cockpit releases weekly. Some versions of Linux distributions closely
> track that weekly release. Other choose particular releases to include,
> based on features and other criteria.
>
> Cockpit now has a stable javascript API and file layout for components
> [2], as well as backwards compatible transport protocol. I hope to post
> more documentation about these guarantees soon.
What about making a 1.0 release?
That's a good question. But let me turn it around. What would the
benefit of 1.0 be?
Cockpit uses continuous integration and delivery. We deliver every week,
and most of them are solid and stable. Certain Linux distributions track
the weekly updates, others pick certain releases and avoid churn for
those users.
So the numbers go up regularly. What would the benefit of having numbers
like "1.110" or "1.202" really be?
I like the systemd or CoreOS model for a project like Cockpit. Cockpit
integrates the system, updates steadily as the system changes, and isn't
a library or API.
But if you have reasons not to do that, I'd love to hear them.
Cheers,
Stef