While we're working on moving more of our SDK repository release processes to execute 'from the cloud', it's become clear that we need a clear template for how this should ideally be done.
The process outlined in this template needs to accommodate the way that we like to work in the SDK Team at Ably. This is just a proposal and, therefore, it is open and expected to change as the views of team members come in. We also expect this first iteration of this template to evolve over time as we learn more about how we like to do releases or technologies change which require us to change our stance.
Creation of this document was triggered by this comment, by @jamienewcomb, asking for acceptance criteria for ably-js when implementing 'Continuous Delivery via GitHub workflow'.
While this pull request remains open, the rendered output can be previewed on the underlying branch.
While we're working on moving more of our SDK repository release processes to execute 'from the cloud', it's become clear that we need a clear template for how this should ideally be done.
The process outlined in this template needs to accommodate the way that we like to work in the SDK Team at Ably. This is just a proposal and, therefore, it is open and expected to change as the views of team members come in. We also expect this first iteration of this template to evolve over time as we learn more about how we like to do releases or technologies change which require us to change our stance.
Creation of this document was triggered by this comment, by @jamienewcomb, asking for acceptance criteria for
ably-jswhen implementing 'Continuous Delivery via GitHub workflow'.While this pull request remains open, the rendered output can be previewed on the underlying branch.