This page holds proposals for new GitHub issues in the Release Management repo.
Proposals to close the existing issues are provided here: Open Issues Consolidated
Multiple APIs in one API Sub-project
ARCHIVED
This section has been updates wits with the outcomes of the dedicated meeting on this topic on 2024-04-12.
...
Herbert's proposal here: Proposal to establish API Families as Working Groups across API Sub Projects · Issue #7 · camaraproject/ReleaseManagement (github.com)
Issue & proposal
GitHub release packages provide a zip file that includes the full API Sub-project repository
...
I had a more complicated version of the previous picture for API versions, but not sure it helps to put this one (and thus to update it to include beta as well.
API Groupings
Grouping of APIs is useful to reduce the number of meetings and reporting load with the increasing number of APIs, and facilitate moving APIs from one family or group to another, or combining related APIs from multiple API Sub-projects into one group.
...
- Each API Sub-projects that contain multiple APIs should
- decide if it should create separate sub-projects for its APIs
- If so, decide on the name and request the API Sub-project creation to cCasey & Evan
- on the API Sub-project pages on the wiki add the list of APIs managed together
- Create one API release tracker page for each API-Subgroup and its API(s)
WISHLIST
- ability to create the API release tracker page data by reading a yaml file in the repo. Tanja de Groot to investigate - aother are welcome to do so too :-)
Whiteboard example
Potential release sequence for a new project:
...