...
- #7 Proposal to establish API Families as Working Groups across API Sub Projects
- Labeled as backlog item, transfer issue to Governance Herbert Damker
- #17 Remove basePath in servers.url as variable
- Proposal to transfer back to Commonalities,
- Expected action: update of Design Guidelines as described in comment by Tanja
- #9 Consolidation Issue for open points release management
- Need status update after the other issues are addressed
- Comments to be reviewed to see if they are all addressed
- .#10 Development and Release Branches
- Done after update/replacement of Camara_Versioning_Guidelines.md with RM results
- Add a FAQ page to the RM wiki with examples. etc
- Put normative versioning guidelines in the API design guidelines (yaml focused) (through PR) and link to the explanation in the RM wiki
- Merge above Camara doc above Camara_Versioning_Guidelines.md file content into RM wiki page
- Add RM guideline short version in RM GitHub projectproject
- #6 Automate API design tests to ensure CAMARA compliance
- Transfer back to Commonalities and let them close it (linting & testing guidelines are worked on there)
- #11 Define mandatory end points URL in each project
- Need a guideline to define "atomic APIs" which have to be implemented completely
- Open point: Where will implementation guidelines be defined?
- Proposed to transfer to Governance
- #12 How to manage version for a API family release
- Done with defined API Release Process
- Add to FAQ when needed
- #5 Process to publish v1.0 of an API
- Addressed with criteria for Stable API versions
- Add explanation to Wiki
- #4 Define Release Management for CAMARA
- Will be closed. Way of working with OGW Product team is addressed in APIBacklog WG
- #13 Consider including Alpha and Beta labels to API versions
- Fully addressed. No beta (similar concept are the Initial API versions). To be closed.
- #14 API Versioning - Aggregation
- backlog item
- #16 Readiness Checklist step 6 update proposal
- Should be updated and moved to RM GitHub project
- New markdown file of checklist will be proposed in an Issue and PR tomorrow by Tanja de Groot
- Create PR in Commonalities to deprecate the Checklist and point to new version in RM Rafal Artych
- Need also to update links to point to the new one
- #15 Add guidance for Info object in apis
- proposal answer in RM page to be copied into issue and issue to be transferred back to commonalities
...