Define and document process for release candidates (RC) versions of schema

[WaleedAshraf]

Currently, we have a lot of feature requests piling up for 2.1.0 (https://github.com/asyncapi/asyncapi/issues/353 zenhub) but there is no clear feedback from the community.

As discussed in SIG meeting #462
We need to define/document RC versions for the schema. This is so that tooling, external packages, users can start using upcoming features early. This way, users can give feedback and make suggestions on the RC version and feedback can be incorporated in the next minor or major release accordingly.

RC would be done only for minor and major versions. patch versions should be rolled out without RC.

Next steps

• Document how/when RC can be released.

[lbroudoux]

Great initiative! Would be happy to help and experimenting the RC release process.

What would be your first ideas or suggestions?

On the OpenAPI Spec side, they seem to work on specific repo branch for WIP and produce different markdown files for keeping the different releases always at hand in the master.

Is the labelling all the candidate issues up-to-date or a new triage has to be done?

[WaleedAshraf]

@lbroudoux Thanks.
I'm interested in this feature: #458
It's been requested at different places. Would be nice to have in RC.

But yeah. We need to first define RC process and document it. I don't think we have labels for all the candidate issues, but I think once we have a process defined, people will automatically start following it.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 60 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation.
Thank you for your contributions ❤️

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 60 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation.
Thank you for your contributions ❤️

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 60 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation.
Thank you for your contributions ❤️

[derberg]

Entire release process, including part about release candidates is already documented here https://github.com/asyncapi/spec/blob/master/RELEASE_PROCESS.md