Prepare for release about specification

[ricardozanini]

@tsurdilo do you have a date in mind? I'll take some time off to work on the SDK then, so we could have more to offer in this new version.

[tsurdilo]

@ricardozanini was hoping for end of the month if possible. I think for release its enough just to update the Go SDK to the latest version of the json schema.
There is no rush so don't worry. WDYT?

[ricardozanini]

I think it's fine! I'll work on the SDK at the end of this week. We should be fine for the release!

[tsurdilo]

I'd like to propose the release candidate: 1.0.0-rc.1
What do you guys think?

[manuelstein]

It feels awkward going from 0.1 straight to 1.0. I'm trying to understand why the bump. If it's for marketing, why would now be a good time? Could maybe KubeCon NA on 17 Nov be a good target? We could bump to 0.2 now and assemble a major release until 9 Nov - our last call just before KubeCon. Until then we have two more calls in Sep and two more in Oct according to our current schedule.

[manuelstein]

On today's community call we discussed options.
Of course, spec is different from software releases.

Generally, version 1.0 often marks the first "complete" set of features that provides a usable version.

Major release numbers are typically bumped when a lot of changes have led to a version that does not provide backwards compatibility.

We have indeed changed enough to say that the major version number should be increased (0->1)
Also, the current status provides a usable set of features, so it can be considered complete enough and out of the draft status.
So, skipping 0.2 and going straight to 1.0 sounds reasonable.

The timing would be best some time before kubecon na, and at best we'd want to use as many channels as possible to announce the 1.0 release, so we can stage release candidates with feature freeze and sufficient time for bugfixing to finish the release some time in October or before Nov 17 latest.

So now, we need a schedule aligned with our community calls :-) any suggestions?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.