Summary
Draft a release sequencing and feature branching strategy for the SDK Plugin Enhancements work. Captures how breaking changes to spec/SDK ship without blocking patch fixes, using buckets of feature branches grouped by checkpoint.
Context
Multiple concurrent features (custom filters, transformation logic, plugin reference implementations) risk stepping on each other if shipped from a single main branch. Temporary feature branches needed despite team preference against them.
Use a clustering approach: group features by related objects that can be deployed independently. Two axes to consider:
- Release timing urgency (which checkpoint each feature targets)
- Implementation dependencies (e.g., transformation work is independent of client changes)
Acceptance criteria
Summary
Draft a release sequencing and feature branching strategy for the SDK Plugin Enhancements work. Captures how breaking changes to spec/SDK ship without blocking patch fixes, using buckets of feature branches grouped by checkpoint.
Context
Multiple concurrent features (custom filters, transformation logic, plugin reference implementations) risk stepping on each other if shipped from a single main branch. Temporary feature branches needed despite team preference against them.
Use a clustering approach: group features by related objects that can be deployed independently. Two axes to consider:
Acceptance criteria