Discuss, Decide & Communicate Release Cadence

[ezgidemirel]

What problem are you facing?

Crossplane and its providers have their own release cycles. Since, Terrajet is announced and ready to be consumed by more people, it would be good to define a release cadence for its GCP, AWS and Azure providers too.

How could Terrajet help solve your problem?

I believe, we should discuss and decide how frequently we may produce a new release for GCP, AWS and Azure jet-providers and document this in the corresponding repositories.

[muvaf]

I think we'll see many bumps to either v1alpha2 or v1beta1 with manually configured resources, which would require minor release. I'd propose that we make sure there is at most 6 weeks between two releases, meaning we can release sooner than 6 weeks but not later. We can adjust depending on how frequent we end up releasing.

[noyoshi]

+1, would like to know when new releases are coming out, as I will be actively using GCP/AWS/Azure terrajet providers :)

[muvaf]

This is blocked by the decision on crossplane/crossplane#2930

[stale]

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.