open-feature / open-feature/spec
Improve Handling of gherkin updates
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 58
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 2
Description
We are creating more and more gherkin updates within this repository, but we do not have a releasing process for them. Hence updates might be difficult, and it is hard to track, if i use this repo as a submodule to see, what changes are added, and that this update of the submodule might break my tests, as there are new tests.
We should think about how we can transparently communicate the gherkin updates via releases or similar mechanics.
Questions in the back of my head:
- can the gherkin tests be released separately as an own version, or do they need to be in sync with the spec version?
- can we utilize release-please to automate this process?
- can we reduce the number of approvers for the gherkin tests?
wdyt?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the repository’s Gherkin tests and reviewing how releases and submodule updates are currently handled. Investigate whether Gherkin updates can be versioned independently or must follow the specification, and assess the proposed release-please approach. Done means a decided, documented process for communicating Gherkin changes and their compatibility impact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- release, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100