-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TI API: Changelog #295
Comments
@FabrizioMoggio my strong recommendation is still to ask for an own repository for the API. It might get more and more difficult to try to provide the release assets for the API within the current repository. To prepare for that you need at least a tagged version here (which you can refer to later in the new repository). |
@hdamker is there a documented procedure to get a dedicated repository? |
The removal of the changelog from the YAML was implemented in #296 |
Please create an issue within API Backlog (see camaraproject/APIBacklog#37 as an example). You can refer to https://github.com/camaraproject/APIBacklog/blob/main/documentation/API%20proposals/APIproposal_Traffic%20Influence_TIM.md. Please add in the issue also the initial Codeowners and Maintainers (I suppose it will be subset out of the EdgeCloud ones). For the transfer of your code to the new repository, you should take a tagged version here in EdgeCloud (which you can refer to within the new repository). cc: @jgarciahospital |
Before proceeding I would like to coordinate with the Edge Cloud WG |
I think the changelog and the tagged release con be produced when the API is stable enough. In my opinion when this list of activities is completed: #282 It anyway good to start a discussion on the creation of a specific repository for the TI API still as part of the Edge Cloud Family |
Discussion started: #313 |
Problem description
The changelog is in the YAML instead it should be in the Changelog.md file
Expected action
Remove the changelog from the YAML file
The text was updated successfully, but these errors were encountered: